provide reason a job is not scheduled #1219
Comments
wihobbs
added a commit
to wihobbs/flux-core
that referenced
this issue
Sep 10, 2024
Problem: autoconf will accept junk at configure time as a valid version, then go off and generate an invalid version.h file. This happens frequently with shallow clones, setups in CI, or other constrained user environments. It has caused new contributors a lot of confusion in the past. Solution: Like flux-framework/flux-sched#1219 suggested, reject invalid versions at configure time and provide appropriate suggestions to the user to remedy this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A question sysadmins and developers get often is "why is job X not running?"
It seems like Fluxion could provide insigths to make this question easier to answer, perhaps even in the output of
flux jobs.Some reasons that we have to manually determine now include:
A simple solution would be for Fluxion to return a
reasonor similar field in the scheduler annotations when it can provide one. This could be made available influx jobs.Another, perhaps longer term solution would be to provide an RPC that unveils a snapshot of the current schedule if one could be made available.
The text was updated successfully, but these errors were encountered: