- 21 Nov, 2014 1 commit
-
-
David Bigagli authored
-
- 20 Nov, 2014 4 commits
-
-
Morris Jette authored
This plugin was never fully completed and should probably be removed from v15.08
-
Morris Jette authored
-
David Bigagli authored
-
Morris Jette authored
-
- 18 Nov, 2014 5 commits
-
-
David Bigagli authored
impact functionality.
-
Morris Jette authored
Copy (i.e. duplicate) information about floating reservations in the highlights section
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
- 17 Nov, 2014 3 commits
-
-
Morris Jette authored
No change to logic
-
Morris Jette authored
The xtree functions are only used in the layouts framework, which isn't currently in use, so I am just commenting out the failing portion of the test for now. It was failing with the message: xtree-test.c:517:F:Core:test_xtree_walk:0: unexpected stop (data, which, level, couple index) expected: 1: 1: 0: 0, got 1: 16: 0
-
Morris Jette authored
-
- 14 Nov, 2014 3 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
- 13 Nov, 2014 9 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Brian Christiansen authored
-
Brian Christiansen authored
Bug 1253
-
Danny Auble authored
-
Danny Auble authored
-
Brian Christiansen authored
-
Brian Christiansen authored
Bug 1255
-
Nathan Yee authored
Bug 1084
-
- 12 Nov, 2014 8 commits
-
-
Morris Jette authored
This applies to salloc, sbatch, and srun. bug 1254
-
Morris Jette authored
The CPU binding should be based upon the CPU_Bind flag rather than Select flag.
-
Hongjia Cao authored
-
David Bigagli authored
-
Danny Auble authored
-
Danny Auble authored
-
Morris Jette authored
Conflicts: src/slurmd/slurmd/req.c
-
Morris Jette authored
Do not requeue a batch job from slurmd daemon if it is killed while in the process of being launched (a race condition introduced in v14.03.9). This partially reverts commit 2bc9bc29
-
- 11 Nov, 2014 2 commits
-
-
David Bigagli authored
-
Danny Auble authored
Conflicts: src/common/pack.c
-
- 10 Nov, 2014 5 commits
-
-
Danny Auble authored
-
Danny Auble authored
This reverts commit bc7ea952. This ended up causing more issues than it solved, reverting.
-
Danny Auble authored
15.08, but this keeps track of allocated cpus as well as usable cpus: meaning if a user requests --hint=nomultithread they are allocated cpus that aren't usable since they requested to only use the 1st thread on each core. reference bug 1247
-
Danny Auble authored
-
Danny Auble authored
with CR_PACK_NODES. Really do commit d388dd67 a different way to get the same info and be able to lay out tasks correctly when --hint=nomultithread. tests on a 4 core 8 thread system are srun -n6 --hint=nomultithread --exclusive whereami | sort -h srun: cpu count 6 0 snowflake0 - MASK:0x1 1 snowflake0 - MASK:0x2 2 snowflake0 - MASK:0x4 3 snowflake0 - MASK:0x8 4 snowflake1 - MASK:0x1 5 snowflake1 - MASK:0x2 and srun -n10 -N5 --hint=nomultithread --exclusive whereami | sort -h srun: cpu count 10 0 snowflake0 - MASK:0x1 1 snowflake0 - MASK:0x2 2 snowflake0 - MASK:0x4 3 snowflake0 - MASK:0x8 4 snowflake1 - MASK:0x1 5 snowflake1 - MASK:0x2 6 snowflake1 - MASK:0x4 7 snowflake2 - MASK:0x1 8 snowflake3 - MASK:0x1 9 snowflake4 - MASK:0x1
-