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
Comments
What about a new "contextual" field in JobInfo that returns the "exit reason" (we could actually call it |
Oh that's a good idea. |
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
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
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
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
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
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
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
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
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
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
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
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
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 influx 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 runflux job --filter=failed
orflux job --filter=canceled
. Perhaps something like:{id} {user} {name} {result} {exception.severity} {exception.type} {exception.note}
Maybe could throw
{returncode}
in as well.The text was updated successfully, but these errors were encountered: