Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no good visual distinction between different types of failure states #76

Open
krancour opened this issue Mar 31, 2022 · 2 comments
Assignees
Milestone

Comments

@krancour
Copy link
Contributor

This is true for both workers and jobs.

Whether something fails, is aborted, times out (other conditions?) you get a red X. You have to dig into the YAML to see the true status.

We should either come up with distinct visual indicators for each state or keep the red X and add a textual description of the state to the summary tab.

In this example, the test-unit-go job was aborted, but it just looks like a failure.

Screen Shot 2022-03-30 at 9 44 47 PM

@krancour krancour added this to the v0.3.0 milestone Mar 31, 2022
@DhairyaBahl
Copy link
Contributor

@krancour I would love to work on this issue. Kindly assign this to me. Time to dive in possible errors for a job 🍻.

@krancour
Copy link
Contributor Author

krancour commented Apr 1, 2022

All set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants