- 14 Apr, 2019 34 commits
-
-
Tim Wickberg authored
Neither salloc/sbatch reset this. I believe reseting each pass, as is done by srun, is the correct behavior, otherwise each separate component will request additional licenses which is unintuitive.
-
Tim Wickberg authored
-
Tim Wickberg authored
For reset, salloc always reset this where sbatch/srun would not. Choosing to go with sbatch/srun's behavior.
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
This should be avoided, but if there are multiple slurm_opt_t entries for a given val (e.g., -W in sbatch vs srun) check that we've found the correct entry. Non-single-character options do not have this issue since they should just use differing LONG_OPT values.
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
A number of validation routines - especially within srun - care whether the variable was set through the environment, or by an explicit CLI option (or embedded in a job script). Provide an easy central test so this can be handled for all arguments.
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
The envvar interface requires some translation to be handled in the same manner of options returned from getopt_long(), as it will intentionally return empty strings for certain variable types. Match OPT_BOOL processing for flags (defined as has_arg = 0 for their getopt_long equivalents).
-
Tim Wickberg authored
-
Tim Wickberg authored
Options will only be printed if set going forward, rather than the somewhat-arbitrary list of options that we've remembered to add here.
-
Tim Wickberg authored
Print each option alongside the value set by slurm_process_option().
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
Used to create trivial set functions when the argument value is simply xstrdup()'d into the associated field in slurm_opt_t.
-
Tim Wickberg authored
-
- 13 Apr, 2019 6 commits
-
-
Marshall Garey authored
After 426abc7f no jobs should be able to be removed from the job_list while backfilling is running. Bug 6621
-
Marshall Garey authored
Timestamps were previously being updated before acquiring mutexes. Change it to update timestamps after mutexes have been acquired. Bug 6621
-
Marshall Garey authored
Bug 6621.
-
Marshall Garey authored
purge_old_job() doesn't ever read or write partition info, so remove the requirement for the partition read lock. Bug 6621
-
Danny Auble authored
-
Marshall Garey authored
The backfill scheduler keeps a local list of job pointers. Since the backfill scheduler yields locks, it's possible for pending jobs to be canceled and purged in these yield periods. The backfill scheduler then has pointers to now invalid memory, and dereferencing those pointers is undefined behavior and may result in a segfault. This commit prevents purging jobs while the backfill scheduler is running. Bug 6621
-