- 08 Feb, 2017 8 commits
-
-
Brian Christiansen authored
-
Brian Christiansen authored
sstat doesn't work on Cray ALPS but works on native Cray setups.
-
Alejandro Sanchez authored
Bug 3444
-
Alejandro Sanchez authored
There are (or at least used to be) places where an exit code of 0 was used to indicate that the job ran successfully to completion. This patch fixes the places where the exit_code was MAX'd out to 1 to indicate that job did not ran successfully to completion. This MAX logic was introduced in commit f305f099. Bug 3444
-
Morris Jette authored
Conflicts: src/slurmctld/job_mgr.c
-
Alejandro Sanchez authored
Jobs preempted with PreemptMode=REQUEUE were incorrectly recorded as REQUEUED in the accounting. Bug 3444
-
Morris Jette authored
-
Morris Jette authored
bug 3448
-
- 07 Feb, 2017 3 commits
-
-
Morris Jette authored
-
Tim Wickberg authored
-
Dominik Bartkiewicz authored
Bug 3447
-
- 03 Feb, 2017 1 commit
-
-
Alejandro Sanchez authored
Bug 3444
-
- 02 Feb, 2017 3 commits
-
-
Morris Jette authored
These were false positive error reports, but should go away now.
-
Tim Shaw authored
Bug 3406.
-
Morris Jette authored
-
- 01 Feb, 2017 4 commits
-
-
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
-
pamxl authored
-
Morris Jette authored
-
Chansup Byun authored
-
- 31 Jan, 2017 12 commits
-
-
Danny Auble authored
-
Danny Auble authored
# Conflicts: # META # NEWS
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
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
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 9 commits
-
-
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.
-
Morris Jette authored
Properly set SLURM_JOB_GPUS environment variable for Prolog. bug 3437
-
Morris Jette authored
-
Morris Jette authored
Clear job's reason of "BeginTime" in a more timely fashion and/or prevents them from being stuck in a PENDING state. There are multiple ways of clearing the reason, especially on a lightly loaded system, but the state can persist indefinitely on a heavily loaded system. bug 3368
-
Danny Auble authored
-
Morris Jette authored
Fix to logic for getting expected start time of existing job ID with explicit begin time that is in the past. Previous logic would compare that (past) begin time with advanced reservations that would compete with it rather than the current time.
-