- 04 May, 2016 1 commit
-
-
Bill Brophy authored
-
- 27 Apr, 2016 1 commit
-
-
Tim Wickberg authored
Compiler errors out preventing these 13 from running without fixing the implied int type for main.
-
- 26 Apr, 2016 1 commit
-
-
Sam Gallop authored
Otherwise miscalculated limit will lead to job cancellation even when well inside the allocated amount. Bug 2660.
-
- 17 Mar, 2016 1 commit
-
-
Tim Wickberg authored
The uid is used as part of the hash function, must remove old reference and recalculate if it may change, otherwise _delete_assoc_hash will not find it again when the association is removed, causing slurmctld to segfault. Bug 2560.
-
- 11 Mar, 2016 1 commit
-
-
Tim Wickberg authored
Return [0-100:2] formatting, rather than [0,2,4,6,8,...] when using a step function. Was inadvertantly broken in 14.11 with commit 5ffdca92. Bug 2535.
-
- 24 Feb, 2016 2 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
- 14 Jan, 2016 1 commit
-
-
Morris Jette authored
Fix for configuration of "AuthType=munge" and "AuthInfo=socket=..." with alternate munge socket path. bug 2348
-
- 07 Jan, 2016 1 commit
-
-
Tim Wickberg authored
Bug 2314.
-
- 05 Jan, 2016 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
- 31 Dec, 2015 1 commit
-
-
Tim Wickberg authored
Later releases have switched over to snprintf to avoid this issue, but 14.11 did not get that patch. Bug 2295.
-
- 15 Dec, 2015 2 commits
-
-
Danny Auble authored
_slurm_rpc_complete_job_allocation. This is a rewrite of 438365ec which didn't catch the job_ptr wasn't in a lock so the memory issue could still of existed. This hopefully fixes all the spots the job_ptr wasn't in the lock. Fixes bug 2146
-
Danny Auble authored
This reverts commit 438365ec.
-
- 25 Nov, 2015 2 commits
-
-
David Bigagli authored
-
David Bigagli authored
-
- 16 Nov, 2015 1 commit
-
-
David Bigagli authored
the Steps keyword.
-
- 13 Nov, 2015 2 commits
-
-
David Bigagli authored
-
Andrew Wettstein authored
but still has running jobs.
-
- 04 Nov, 2015 1 commit
-
-
Brian Christiansen authored
Bug 2095
-
- 22 Oct, 2015 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
- 19 Oct, 2015 1 commit
-
-
David Bigagli authored
-
- 09 Oct, 2015 1 commit
-
-
David Bigagli authored
about job setup.
-
- 07 Oct, 2015 2 commits
-
-
Danny Auble authored
-
Danny Auble authored
database but the start record hadn't made it yet.
-
- 06 Oct, 2015 3 commits
-
-
Thomas Cadeau authored
bug 2011
-
Danny Auble authored
','.
-
Morris Jette authored
bug 1999
-
- 05 Oct, 2015 1 commit
-
-
jette authored
-
- 03 Oct, 2015 1 commit
-
-
Morris Jette authored
Don't requeue RPC going out from slurmctld to DOWN nodes (can generate repeating communication errors). bug 2002
-
- 02 Oct, 2015 1 commit
-
-
Morris Jette authored
This will only happen if a PING RPC for the node is already queued when the decision is made to power it down, then fails to get a response for the ping (since the node is already down). bug 1995
-
- 30 Sep, 2015 3 commits
-
-
Morris Jette authored
If a job's CPUs/task ratio is increased due to configured MaxMemPerCPU, then increase it's allocated CPU count in order to enforce CPU limits. Previous logic would increase/set the cpus_per_task as needed if a job's --mem-per-cpu was above the configured MaxMemPerCPU, but NOT increase the min_cpus or max_cpus varilable. This resulted in allocating the wrong CPU count.
-
Brian Christiansen authored
Continuation of 1252d1a1 Bug 1938
-
Morris Jette authored
Requeue/hold batch job launch request if job already running. This is possible if node went to DOWN state, but jobs remained active. In addition, if a prolog/epilog failed DRAIN the node rather than setting it down, which could kill jobs that could continue to run. bug 1985
-
- 29 Sep, 2015 3 commits
-
-
Morris Jette authored
Previous logic would not report termiation siganl, only exit code, which could be meaningless.
-
Brian Christiansen authored
Bug 1938
-
Brian Christiansen authored
Bug 1984
-
- 28 Sep, 2015 1 commit
-
-
Morris Jette authored
When nodes have been allocated to a job and then released by the job while resizing, this patch prevents the nodes from continuing to appear allocated and unavailable to other jobs. Requires exclusive node allocation to trigger. This prevents the previously reported failure, but a proper fix will be quite complex and delayed to the next major release of Slurm (v 16.05). bug 1851
-
- 23 Sep, 2015 1 commit
-
-
Danny Auble authored
The 2 came from the nodelist being "None assigned", which would be treated as 2 hosts when sent into hostlist.
-