- 03 May, 2016 6 commits
-
-
Tim Wickberg authored
-
Danny Auble authored
-
Danny Auble authored
-
Brian Christiansen authored
-
Tim Wickberg authored
-
Eric Martin authored
-
- 02 May, 2016 1 commit
-
-
Danny Auble authored
requesting the RUNNING state.
-
- 29 Apr, 2016 4 commits
-
-
Danny Auble authored
Backport of commit cca1616b from 16.05
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
- 28 Apr, 2016 4 commits
-
-
Morris Jette authored
Some systems return EWOULDBLOCK rather than EAGAIN on recv() failure This is an enhancement to commit af47b4b2
-
Artem Polyakov authored
See bug 2672 for details
-
Tim Wickberg authored
-
Danny Auble authored
of Slurm.
-
- 27 Apr, 2016 4 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
Compiler errors out preventing these 13 from running without fixing the implied int type for main.
-
Danny Auble authored
though we decided to push that fix to 16.05 since this has been broken for a while and no one has complained.
-
Morris Jette authored
Avoid error message of "Requested cpu_bind option requires entire node to be allocated; disabling affinity" being generated in some cases where task/affinity and task/cgroup plugins used together.
-
- 26 Apr, 2016 7 commits
-
-
Danny Auble authored
-
Danny Auble authored
restart of the slurmctld.
-
Morris Jette authored
On some systems the char_to_val was not being put into the plugin, resulting in the following error: slurmstepd: [23.0]: symbol lookup error: /home/jette/SLURM/install_smd/lib/slurm/task_cgroup.so: undefined symbol: char_to_val The problem was fixed by declaring the function "static". The function was name was also updated with a leading "_" to indicate the function is local to that module.
-
Danny Auble authored
-
René Genz authored
-
Tim Wickberg authored
-
Sam Gallop authored
Otherwise miscalculated limit will lead to job cancellation even when well inside the allocated amount. Bug 2660.
-
- 23 Apr, 2016 1 commit
-
-
Tim Wickberg authored
in the slurmdbd segfaulting. Bug 2656
-
- 20 Apr, 2016 2 commits
-
-
Morris Jette authored
burst_buffer/cray - Don't call Datawarp "paths" function if script includes only create or destroy of persistent burst buffer. Some versions of Datawarp software return an error for such scripts, causing the job to be held. bug 2624
-
Morris Jette authored
No change in any logic or definitions
-
- 15 Apr, 2016 1 commit
-
-
Morris Jette authored
-
- 14 Apr, 2016 1 commit
-
-
Morris Jette authored
If a job fails stage in, set its reason to BurstBufferOperation with a string describing what happened. Previously the reason was set to AdminHeld on stage-in failure.
-
- 13 Apr, 2016 2 commits
-
-
Morris Jette authored
-
Danny Auble authored
that wasn't set up correctly.
-
- 12 Apr, 2016 3 commits
-
-
Morris Jette authored
power/cray - Fix bug introduced in 15.08.10 preventin operation in many cases. bug 2628
-
Morris Jette authored
-
Morris Jette authored
Was printing integer using %u format
-
- 11 Apr, 2016 4 commits
-
-
Morris Jette authored
burst_buffer/cray - Fix for script creating or deleting persistent buffer would fail "paths" operation and hold the job. bug 2624
-
Danny Auble authored
and it doesn't meet basic requirements.
-
Tim Wickberg authored
-
Morris Jette authored
The gprof tool is showing most time is being consumed by the bit_test() function as called from the select plugin, which in turn was called by the backfill scheduler. These changes replace the for loop end-points. Previous logic tested for all possible nodes. The new logic identifes the first and last bit set in the node bitmap and uses those end-points instead. Node the logic to find the first and last bits set starts off with a word-based search (testing for a 64-bit zero value rather than testing each individual bit). The net result is a small performance improvement. bug 2588
-