Mark Grondona
Mark Grondona
> How does slurm handle libpmi2, is it just always installed in /usr/lib64? Yes. > my first thought would be to treat it as an alternative, in the update-alternatives sense,...
FYI, there is an optparse flag to hide subcommands. We should do the same for `flux job list-inactive` and `flux job list-ids`. I do find it useful sometimes to dump...
> and also aborts if stdout is a tty (with a message to try flux-jobs(1)) Oh, clever idea.
> currently the job-archive errors out if no statedir is specified. how to deal with this with a job-db module? obviously don't want to error out and have no job-listing??...
What if instead of trying to make sure the journal events are delayed until the associated kvs commit is complete, we added an entry to the journal for jobs _after_...
There is a huge opportunity for enhanced tools here since the full "resource set" for every job that ran will be available in the KVS or the job archive database....
Here's something I just hacked together that could be the start of a solution here: ```python #!/usr/bin/python3 import sys from datetime import datetime import flux from flux.job import job_list_inactive from...
Just added support for query of active jobs and their remaining time (I can rework this script to provide a better interface a bit later) ```python #!/usr/bin/python3 import sys from...
Oh, good thinking! I had in the back of my mind that `jobspec-update` events would be for the instance only and would be ignored by the shell, though the default...
Related discussion in #2371