- 10 Feb, 2017 7 commits
-
-
Brian Christiansen authored
-
Brian Christiansen authored
Was sending the response_rec for every job on a normal cluster when it only needs to send when the allocation was from a different cluster.
-
Brian Christiansen authored
The response_cluster_rec was pointing to the conf's cluster_name which gets free'd and reallocated on a reconfig. So the cluster_name was pointing to garbage.
-
Brian Christiansen authored
so that it will only run the tests if you have check.
-
Isaac Hartung authored
-
Isaac Hartung authored
-
Brian Christiansen authored
If size is 0, it will allocate 0 + 2. 2 for the magic and the size. But xmalloc will then retun the pointer pointing past the newly allocated memory (p[2]) which can cause a segfault.
-
- 09 Feb, 2017 15 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
burst_buffer/cray - Support default pool which is not the first pool reported by DataWarp and log in Slurm when pools that are added or removed from DataWarp. bug 3453
-
Brian Christiansen authored
-
Brian Christiansen authored
-
Morris Jette authored
-
Morris Jette authored
-
Brian Christiansen authored
Refactor the loading in of plugins.
-
Brian Christiansen authored
Instead of creating static functions everytime.
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
This reverts commit fd690a9c.
-
Danny Auble authored
-
Artem Polyakov authored
-
- 08 Feb, 2017 15 commits
-
-
Danny Auble authored
-
Danny Auble authored
was there for jobs and steps, but for no real reason. I couldn't see a reason anyway.
-
Danny Auble authored
Add missing option for PURGE_JOB which is different than the others and was missed on the changes made when adding the usage table flushes.
-
Brian Christiansen authored
-
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
-
Morris Jette authored
bug 3448
-
Danny Auble authored
i.e. AcctGatherInterconnectType = ofed,none Bug 3412
-
Danny Auble authored
compatibility.
-
- 07 Feb, 2017 3 commits
-
-
Danny Auble authored
Actual code change to make it happen. Just renaming things, nothing really changed.
-
Danny Auble authored
-
Danny Auble authored
-