- 06 Jul, 2016 4 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
Fix for invalid array pointer when creating advanced reservation when job allocations span heterogeneous nodes (differing core or socket counts). bug 2876
-
- 05 Jul, 2016 8 commits
-
-
Morris Jette authored
Prevent backfill scheduler from starting a second "singleton" job if another one started during a backfill sleep. related to bug 2808
-
Tim Wickberg authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Tim Wickberg authored
-
- 04 Jul, 2016 1 commit
-
-
Morris Jette authored
Previous logic required listing each task of job array individually. For example --dependency="afterany:123_4:123_5" can not be expressed as --dependency="afterany:123_[4-5]". bug 2644
-
- 02 Jul, 2016 3 commits
-
-
Danny Auble authored
we have the pids added to the system correctly. Most likely related to bug 2874
-
Danny Auble authored
-
Danny Auble authored
-
- 01 Jul, 2016 7 commits
-
-
Danny Auble authored
Bug 2612 (and possibly others)
-
Danny Auble authored
back to the slurmctld.
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
- 30 Jun, 2016 14 commits
-
-
Morris Jette authored
Add salloc/sbatch/srun --spread-job to distribute tasks over as many nodes as possible. This also treats the --ntasks-node-node option as a maximum value. For example "srun -n16 --ntasks-per-node=2 --spread-job ..." will run the job on at least 8 nodes (with 2 tasks each), but will attempt to use as many nodes as possible up to the task count (1 task per node). bug 2732
-
Brian Christiansen authored
-
Brian Christiansen authored
prctld(PR_GET_NAME) >= 2.6.11
-
Brian Christiansen authored
This reverts commit d9d36a33.
-
Danny Auble authored
-
Danny Auble authored
-
Morris Jette authored
-
Alejandro Sanchez authored
In bug #1499, customer asked to precisely identify which srun options apply to job allocations, which to step allocations and which apply to both. So the srun man page has been updated with this information.
-
Morris Jette authored
Move test for job wait reason value of BurstBufferResources and BurstBufferStageIn later in the scheduling logic. This will result in job reasons related to QOS, account, and partition limits to be displayed instead of burst buffer (if applicable) bug 2835
-
Danny Auble authored
id wasn't able to be made.
-
Morris Jette authored
-
Morris Jette authored
Discovered in testing that the cnselect command only returns information about KNL node state for nodes that are already up. If a node is down or in the process of booting, only capmc as the state which will be in effect when the boot completes. This change merges the old logic (reading state from capmc) with new logic (merging new state information from cnselect into the capmc data), which results in the most complete picture possible about the KNL state. bug 2850
-
Morris Jette authored
-
Morris Jette authored
-
- 29 Jun, 2016 3 commits
-
-
Tim Wickberg authored
Values are already time_t / printed with %ld so this should keep Y2038 at bay. Bug 2862.
-
Tim Wickberg authored
-
Danny Auble authored
-