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

indicate held jobs in the INFO column of flux jobs output #6430

Merged
merged 3 commits into from
Nov 13, 2024

Conversation

grondo
Copy link
Contributor

@grondo grondo commented Nov 13, 2024

This PR implements @ryanday36's suggestion in #6426. It extends the flux jobs {contextual_info} field (INFO) to check for a priority of 0 and prints held if urgency is also zero, otherwise priority-hold.

Copy link
Member

@garlick garlick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Problem: Held jobs (those with priority=0) are not denoted in default
flux-jobs(1) output, but this would be useful for admins and users
to quickly determine why these jobs are not being scheduled.

Update the `contextual_info` property of the `JobInfo` class (which
supplies the content for the INFO column) to return "held" for jobs
with urgency=0 and "priority-hold" for jobs with priority=0.

Fixes flux-framework#6426
Problem: The documentation of the `contextual_info` field in
flux-jobs(1) does not include that "held" is a possible result.

Update it.
Problem: No tests in the testsuite ensure that the `contextual_info`
field in flux-jobs output indicates held jobs.

Add a couple tests that ensure the INFO field presents held jobs as
either "held" or "priority-hold".
@grondo
Copy link
Contributor Author

grondo commented Nov 13, 2024

Thanks! I'll set MWP.

@mergify mergify bot merged commit 83d7b57 into flux-framework:master Nov 13, 2024
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants