- 12 Jun, 2015 1 commit
-
-
Brian Christiansen authored
Bug 1743
-
- 11 Jun, 2015 5 commits
-
-
Brian Christiansen authored
Prevent double free.
-
Brian Christiansen authored
-
Brian Christiansen authored
Bug 1733
-
Didier GAZEN authored
In your node_mgr fix to keep rebooted nodes down (commit 9cd15dfe), you forgot to consider the case of nodes that are powered up but are responding after ResumeTimeout seconds (the maximum time permitted). Such nodes are marked DOWN (because they didn't respond within ResumeTimeout seconds) than should become silently available when ReturnToService=1 (as stated in the slurm.conf manual) With your modification when such nodes are finally responding, they are seen as rebooted nodes and remain in the DOWN state (with the new reason: Node unexpectedly rebooted) even when ReturnToService=1 ! Correction of commit 3c2b46af
-
Didier GAZEN authored
-
- 10 Jun, 2015 3 commits
-
-
Morris Jette authored
-
Didier GAZEN authored
In your node_mgr fix to keep rebooted nodes down (commit 9cd15dfe), you forgot to consider the case of nodes that are powered up but are responding after ResumeTimeout seconds (the maximum time permitted). Such nodes are marked DOWN (because they didn't respond within ResumeTimeout seconds) than should become silently available when ReturnToService=1 (as stated in the slurm.conf manual) With your modification when such nodes are finally responding, they are seen as rebooted nodes and remain in the DOWN state (with the new reason: Node unexpectedly rebooted) even when ReturnToService=1 ! My patch to obtain the correct behaviour:
-
Morris Jette authored
Equivalent fix as e1a00772 for select/serial rather than select/cons_res
-
- 09 Jun, 2015 7 commits
-
-
David Bigagli authored
-
Morris Jette authored
1. I submit a first job that uses 1 GPU: $ srun --gres gpu:1 --pty bash $ echo $CUDA_VISIBLE_DEVICES 0 2. while the first one is still running, a 2-GPU job asking for 1 task per node waits (and I don't really understand why): $ srun --ntasks-per-node=1 --gres=gpu:2 --pty bash srun: job 2390816 queued and waiting for resources 3. whereas a 2-GPU job requesting 1 core per socket (so just 1 socket) actually gets GPUs allocated from two different sockets! $ srun -n 1 --cores-per-socket=1 --gres=gpu:2 -p testk --pty bash $ echo $CUDA_VISIBLE_DEVICES 1,2 With this change #2 works the same way as #3. bug 1725
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Morris Jette authored
-
David Bigagli authored
option.
-
- 05 Jun, 2015 8 commits
-
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
Only going to do this in the master as it may affect scripts. This reverts commit 454f78e6. Conflicts: NEWS
-
Morris Jette authored
bug 1724
-
Nicolas Joly authored
-
Nicolas Joly authored
-
Morris Jette authored
-
- 04 Jun, 2015 8 commits
-
-
David Bigagli authored
-
David Bigagli authored
-
Morris Jette authored
-
Veronique Legrand authored
Previously the test would generate an error if the default partition contained less than 3 nodes bug 1720
-
Nicolas Joly authored
-
Nancy Kritkausky authored
-
David Bigagli authored
-
David Bigagli authored
-
- 03 Jun, 2015 1 commit
-
-
Morris Jette authored
switch/cray: Refine logic to set PMI_CRAY_NO_SMP_ENV environment variable. Rather than testing for the task distribution option, test the actual task IDs to see fi they are monotonically increasing across all nodes. Based upon idea from Brian Gilmer (Cray).
-
- 02 Jun, 2015 3 commits
-
-
Danny Auble authored
-
Danny Auble authored
afterward cause a divide by zero error.
-
Danny Auble authored
corruption if thread uses the pointer basing validity off the id. Bug 1710
-
- 01 Jun, 2015 3 commits
-
-
David Bigagli authored
-
Nicolas Joly authored
-
Morris Jette authored
Disable test with select/linear and only one node
-
- 30 May, 2015 1 commit
-
-
Danny Auble authored
-