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

flux-jobs: support output format to show exception notes #4946

Closed
chu11 opened this issue Feb 16, 2023 · 2 comments
Closed

flux-jobs: support output format to show exception notes #4946

chu11 opened this issue Feb 16, 2023 · 2 comments
Assignees

Comments

@chu11
Copy link
Member

chu11 commented Feb 16, 2023

While trying to write up a simple tutorial on flux job cancel, I realized that we have no easy way for users to check for exception notes other than writing their own format in flux jobs. This is fine, but exceptions are a bit long to write formats for.

A format for listing failure information in flux jobs would probably be useful when users run flux job --filter=failed or flux job --filter=canceled. Perhaps something like:

{id} {user} {name} {result} {exception.severity} {exception.type} {exception.note}

Maybe could throw {returncode} in as well.

@grondo
Copy link
Contributor

grondo commented Feb 17, 2023

Maybe could throw {returncode} in as well.

What about a new "contextual" field in JobInfo that returns the "exit reason" (we could actually call it exit_reason though that could be confusing because not all inactive jobs actually exited), i.e. if the job is inactive it returns some text describing the exception if one occurred, otherwise a string with the return code, perhaps in shell-like form, e.g. Exit 0, Exit 1, Killed, Terminated, etc. Then we might have room for start and end times which might be nice.

@chu11
Copy link
Member Author

chu11 commented Feb 17, 2023

What about a new "contextual" field in JobInfo that returns the "exit reason" (we could actually call it exit_reason though that could be confusing because not all inactive jobs actually exited), i.e. if the job is inactive it returns some text describing the exception if one occurred, otherwise a string with the return code, perhaps in shell-like form, e.g. Exit 0, Exit 1, Killed, Terminated, etc. Then we might have room for start and end times which might be nice.

Oh that's a good idea.

@chu11 chu11 self-assigned this Mar 27, 2023
chu11 added a commit to chu11/flux-core that referenced this issue Mar 31, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue Apr 1, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue Apr 1, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue Apr 1, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue Apr 4, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 9, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 11, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 11, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 12, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 12, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 16, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
chu11 added a commit to chu11/flux-core that referenced this issue May 16, 2023
Problem: There are a number of fields in flux-jobs that are available
to help users get details about how or why their job exited / finished / ended.
However, it is scattered across several fields.  It would be convenient
if there were just one field that collated that information.

Solution: Support a new "inactive_reason" output field.  It will output if a
job was canceled, signaled, timedout, or exited normally.  Other contextual
information will be output when available.

Fixes flux-framework#4946
@mergify mergify bot closed this as completed in ceeed14 May 16, 2023
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