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

cylc gscan: add failed information #1244

Closed
kaday opened this issue Nov 28, 2014 · 10 comments
Closed

cylc gscan: add failed information #1244

kaday opened this issue Nov 28, 2014 · 10 comments
Assignees
Milestone

Comments

@kaday
Copy link
Contributor

kaday commented Nov 28, 2014

From issue1164 part two:
" Request from BOM:

  • in cases where the suite has failed task, the name of the failed task (for multiple failed tasks, I suppose it could be either the first failed task or number of the failed tasks)"
@kaday kaday added this to the later milestone Nov 28, 2014
@kaday kaday self-assigned this Dec 3, 2014
@kaday kaday modified the milestones: some-day, later Dec 3, 2014
@hjoliver
Copy link
Member

On hover-over, gscan now shows the number of tasks in each state (including failed).

Names of failed tasks - maybe that's worth doing, I'm not sure. Is failed fundamentally more important than all the other states (it certainly is quite important, but what about submit-failed, expired, retrying, ...). We can't list them all in gscan hover-over, for big suites. @cylc/core - opinions on whether to close this or not?

@hjoliver hjoliver changed the title cylc gsummary: add failed information cylc gscan: add failed information Feb 11, 2016
@kaday
Copy link
Contributor Author

kaday commented Feb 12, 2016

I think that failed is far more important especially after having just started a 50:50 secondment where I am working closer to the operational side and I am seeing how they are using gscan. If the rest of the @cylc/core agree I will make this a priority now.

@matthewrmshin
Copy link
Contributor

I think a good interface for this is to print out a list of, say, the most recent 10 (configurable?) task IDs that fall into each category. For failed tasks, the total should be a small number, so would normally display everything relevant. Otherwise, we can print the 10 most recent task IDs, then say something like e.g. and 62438 more.

@arjclark
Copy link
Contributor

As this list can get potentially quite long and render the hover overs useless, what might be nicer instead would be to have the ability to get a quick listing of tasks in a particular state of interest via a right click menu or something that opens up a popup with a scroll bar window if needed.

@matthewrmshin
Copy link
Contributor

(To elaborate my comment above, I am thinking of a hover-over for each state, instead of an overall hover-over, like we do now.)

@kaday
Copy link
Contributor Author

kaday commented Feb 12, 2016

Matt's idea is what I was considering but I had not thought to limit it, which I think is an ace idea and will allow the hover to still work.

@hjoliver
Copy link
Member

Yeah, limiting to a max number of tasks makes the hover-over workable. We could do both: hover-over for minimal info about a max of 10 tasks, right click menu to get more detailed information about all tasks in that state in a popup window?

@kaday kaday removed their assignment May 28, 2016
@kaday
Copy link
Contributor Author

kaday commented May 28, 2016

The PSA's here said it would really help them if the 10 most recently failed tasks were listed in the hover-over.

@hjoliver
Copy link
Member

@kaday - 'scuse my ignorance, but a "PSA"?

@benfitzpatrick
Copy link
Contributor

(Our acronym for operational suite controller)

@benfitzpatrick benfitzpatrick modified the milestones: later, some-day Jun 3, 2016
@matthewrmshin matthewrmshin modified the milestones: next release, later Jun 10, 2016
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

6 participants