- 29 Nov, 2017 7 commits
-
-
Danny Auble authored
Bug 4450
-
Danny Auble authored
the libslurmfull.
-
Danny Auble authored
In my testing with the cray job_submit plugin enabled it caused a delay of the last step most likely because the gres wasn't ready quick enough.
-
Brian Christiansen authored
This reverts commit f9977ee5. Since it's not needed in 17.11
-
Brian Christiansen authored
-
Brian Christiansen authored
slurm_load_job() prior to 17.11 returns the error code in errno and not in rc. With the addition of 47175901 if a job is removed from memory before sbatch checks for the job again, sbatch could get in an loop checking for the job. This only happens if you have a very small MinJobAge (<10) -- which is not recommended.
-
Morris Jette authored
-
- 28 Nov, 2017 33 commits
-
-
Danny Auble authored
-
Morris Jette authored
-
Doug Jacobsen authored
Bug 4445
-
Doug Jacobsen authored
Bug 4444
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well
-
Tim Wickberg authored
-
Danny Auble authored
-
Morris Jette authored
-
Danny Auble authored
Bug 4323
-
Morris Jette authored
Bug 4299
-
Felip Moll authored
Bug 4299
-
Brian Christiansen authored
-
Tim Wickberg authored
Amend commit 4b76750a.
-
Felip Moll authored
Bug 4299
-
Felip Moll authored
Bug 4408.
-
Morris Jette authored
-
Doug Jacobsen authored
bug 4442
-
Doug Jacobsen authored
Bug 4440
-
Doug Jacobsen authored
bug 4443
-
Doug Jacobsen authored
bug 4442
-
Morris Jette authored
-
Morris Jette authored
bug 4442
-
Doug Jacobsen authored
Bug 4440
-
Doug Jacobsen authored
bug 4443
-
Morris Jette authored
-
Doug Jacobsen authored
bug 4441
-
Tim Wickberg authored
-
Isaac Hartung authored
Bug 4306.
-
Danny Auble authored
Bug 4416
-
Brian Christiansen authored
Continuation of d4a485d2
-
Tim Wickberg authored
Fix regression added in commit 9df82091. Bug 4406.
-
Marshall Garey authored
to fix issue where job ordering causes wrong unused wall. The "order by" part of the original sql query was wrong. I had a situation where I had 2 jobs in an updated reservation, but instead of adding their times together, they were overwriting their times. This happened because of the ordering of the rows, where the reservation got split up because of the "order by job.time_start". That was simply wrong. Bug 4406
-