- 02 Feb, 2017 7 commits
-
-
Morris Jette authored
See if this tactic can be used to make a bunch of Coverity errors go away.
-
Morris Jette authored
Add NO_VAL32 (same value as NO_VAL) and add INFINITE32 (same value as INFINITE) These now match the NO_VAL16, NO_VAL64, INFINITE16 and INFINITE64 value types
-
Morris Jette authored
Coverity does not recongize the getopt_long() function's required argument, so Coverity reported errors whenever a NULL optarg value resulted in an error. This change adds a bunch of tests for NULL optarg value and skips it's processing.
-
Tim Shaw authored
Bug 3122.
-
Tim Shaw authored
In preparation for Bug 3122
-
Morris Jette authored
-
Morris Jette authored
-
- 01 Feb, 2017 11 commits
-
-
Morris Jette authored
-
Morris Jette authored
Fix srun I/O race condtion to eliminate a error message that might be generated if the application exits with outstanding stdin. bug 3166
-
Morris Jette authored
-
pamxl authored
-
Morris Jette authored
-
Chansup Byun authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Dominik Bartkiewicz authored
-
Tim Wickberg authored
Minor style fix while in nearby lines. No functional change.
-
Dominik Bartkiewicz authored
Improve performance by looping once over the bitstring rather than three times. This also allows us to remove some temporary bitstring variables that were holding an inverted version.
-
- 31 Jan, 2017 17 commits
-
-
Danny Auble authored
# Conflicts: # META # NEWS
-
Danny Auble authored
-
Danny Auble authored
# Conflicts: # META # NEWS
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Tim Wickberg authored
-
Brian Christiansen authored
Update corresponding unit test check as well.
-
Dominik Bartkiewicz authored
Use instead of the repeated construction of: bit_not(b); bit_and(a, b); bit_not(b); to avoid two addition iterations.
-
Alejandro Sanchez authored
-
Brian Christiansen authored
-
Brian Christiansen authored
Can't set the job_id of a will_run will_run job prior to creating the job. Invalidates the jobs for non-slurmuser jobs. Also not burning a jobid could make the will_run job not be distinguishable in the logs. Will handle the federation aspect of this in 17.11. Bug 3436
-
Dominik Bartkiewicz authored
job_write_lock and sleep a second before grabbing it again. This should probably be made configurable later on.
-
Danny Auble authored
-
- 30 Jan, 2017 5 commits
-
-
Danny Auble authored
-
Danny Auble authored
# Conflicts: # src/slurmctld/proc_req.c
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
e3a7bdcc f9804256 d72b13f2 Reference bug 3366 If you are running on a Bluegene system we rely on the prolog to take us out of configuring state. These commits work good for system rebooting the nodes where the prolog is running, but in the case of Bluegene this is the opposite desire :). These commits on a Bluegene pretty much make it so a batch job never gets launched.
-