- 11 Dec, 2015 3 commits
-
-
Morris Jette authored
Conflicts: META NEWS
-
Morris Jette authored
-
Morris Jette authored
-
- 10 Dec, 2015 8 commits
-
-
Danny Auble authored
The problem comes from situations where a node range is given, leaving the task count at NO_VAL is the desired behavior in this case.
-
Danny Auble authored
so we can set it correctly before tasks are set.
-
Morris Jette authored
-
Tim Wickberg authored
-
Danny Auble authored
-
Tim Wickberg authored
messages like FAILURE: 1 scontrol show assoc_mgr did not show correct information (6 != 5). to happen erroneously.
-
David Bigagli authored
-
Tim Wickberg authored
The error messages associated with these are: /home/tim/slurm/src/common/callerid.c:337:21: warning: address of array 'entryp->d_name' will always evaluate to 'true' [-Wpointer-bool-conversion] else if (!entryp->d_name) ~~~~~~~~~^~~~~~ 1 warning generated. /home/tim/slurm/src/common/gres.c:831:19: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare] if ((tmp_uint64 < 0) || (tmp_uint64 >= NO_VAL)) { ~~~~~~~~~~ ^ ~ 1 warning generated. /home/tim/slurm/src/slurmctld/node_mgr.c:1684:26: warning: if statement has empty body [-Wempty-body] if (first_new == NULL); ^ /home/tim/slurm/src/slurmctld/node_mgr.c:1684:26: note: put the semicolon on a separate line to silence this warning /home/tim/slurm/src/slurmctld/node_mgr.c:1756:26: warning: if statement has empty body [-Wempty-body] if (first_new == NULL); ^ /home/tim/slurm/src/slurmctld/node_mgr.c:1756:26: note: put the semicolon on a separate line to silence this warning /home/tim/slurm/src/slurmctld/node_mgr.c:1830:26: warning: if statement has empty body [-Wempty-body] if (first_new == NULL); ^ /home/tim/slurm/src/slurmctld/node_mgr.c:1830:26: note: put the semicolon on a separate line to silence this warning /home/tim/slurm/src/plugins/switch/generic/switch_generic.c:837:27: warning: address of array 'if_rec->ifa_addr->sa_data' will always evaluate to 'true' [-Wpointer-bool-conversion] if (!if_rec->ifa_addr->sa_data) ~~~~~~~~~~~~~~~~~~~^~~~~~~
-
- 09 Dec, 2015 17 commits
-
-
Morris Jette authored
news
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
no matter who calls the function.
-
Danny Auble authored
-
Danny Auble authored
function to common.c from last commit.
-
Alejandro Sanchez authored
through sacctmgr.
-
Morris Jette authored
select/cray: Prevent NHC from running more than once per job or step. bug 2192
-
Tim Wickberg authored
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
In both sched/basic and backfill: If a job can not be started due to some account/qos limit, then don't start other jobs which could delay jobs. The old logic would skip the job and start other jobs, which could delay the higher priority job. bug 2129
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
Without this change, one of the two job steps could consume all memory and delay the second step.
-
Brian Christiansen authored
-
- 08 Dec, 2015 12 commits
-
-
Morris Jette authored
Conflicts: configure
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Brian Christiansen authored
-
Tim Wickberg authored
This also corrects per user burst buffer space calculation
-
Morris Jette authored
-
Morris Jette authored
-
Brian Christiansen authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-