- 18 Jan, 2018 1 commit
-
-
Danny Auble authored
itself. Bug 4638
-
- 17 Jan, 2018 3 commits
-
-
Morris Jette authored
-
Morris Jette authored
Test 3.11, file inc3.11.9 only runs for some configurations, but assumes no leading zeros in node name suffix. When run with nodes named "nid[00001-00005]", the test converted the last number to it's numeric for and as making requests for "nid[00001-5]", which would fail.
-
Morris Jette authored
-
- 16 Jan, 2018 5 commits
-
-
Morris Jette authored
Fix output file containing "%t" (task ID) for heterogeneous job step to be based upon global task ID rather than task ID for that component of the heterogeneous job step.
-
Morris Jette authored
This expands some comments Explicitly sets some pointers to NULL after memcpy (these are redundant, but add clarity) and Move a memcpy to avoid modifying the wrong values
-
Morris Jette authored
-
Danny Auble authored
-
Morris Jette authored
Fix for possible memory corruption in srun when running heterogeneous job steps. bug 4626
-
- 12 Jan, 2018 9 commits
-
-
Dominik Bartkiewicz authored
This partially reverts 89bcd975 and aac6bd39 Turns out you can't use a list_for_each and lock something inside the list_for_each function that does a lock without the write lock. Bug 4611
-
Danny Auble authored
This reverts commit ff3e77f4.
-
Danny Auble authored
This partially reverts 89bcd975 and aac6bd39 Turns out you can't use a list_for_each and lock something inside the list_for_each function that does a lock without the write lock. Bug 4611
-
Tim Wickberg authored
Otherwise undocumented, and does not do anything. Will be removed in 18.08.
-
Morris Jette authored
-
Morris Jette authored
-
Dominik Bartkiewicz authored
Fix job array dependency with "aftercorr" option and some task arrays in the first job fail. This fix lets all task array elements that can run proceed rather than stopping all subsequent task array elements. Bug 4590
-
Felip Moll authored
Creating a copy of the actual environment in env->env defines a new pointer, then next call to setup_env and setenvf doesn't define variables in the global environment but in this new copy. Bug 4615
-
Morris Jette authored
This fixes the problem introduced in by commit 777a45f9 and maintains proper PMIx operation. bugs 4132 and 4615
-
- 11 Jan, 2018 6 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
node_feature/knl_cray - Fix memory leak that can occur during normal operation. This will happen when an update request for a specific node happens.
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
If CnselectPath and/or SyscfgPath defined in knl_cray.conf file and slurmctld reconfigured, the original values of those paraemters would be over-written and their memory leaked.
-
- 10 Jan, 2018 3 commits
-
-
Felip Moll authored
Use FREE_NULL_BUFFER instead, otherwise we could attempt to free_buffer a second time if we jump to the rwfail label. bug4491
-
Isaac Hartung authored
to preempt other eligible jobs. Bug 4279
-
Brian Christiansen authored
Missing from 390da8cf Bug 4595
-
- 09 Jan, 2018 5 commits
-
-
Brian Christiansen authored
slurmdb_pack_assoc_usage() will assert with a NULL usage ptr.
-
Brian Christiansen authored
7d9a75df uncovered that slurmdb_pack_assoc_usage() expects a usage ptr.
-
Philip Kovacs authored
Bug 4469
-
Dominik Bartkiewicz authored
-
Danny Auble authored
This is a continuation to c539d346 where this should had been removed in the first place.
-
- 08 Jan, 2018 5 commits
-
-
Dominik Bartkiewicz authored
Bug 4127
-
Brian Christiansen authored
-
Alejandro Sanchez authored
bug 4539
-
Alejandro Sanchez authored
When --mail-type option isn't requested with ARRAY_TASKS, we need somehow to summarize the different states each task finished in the array. We've added a new ARRAY_TASK_REQUEUED flag to the array_flags to indicate that at least one task was requeued. Also the logic now detects if at least one task failed and/or if otherwise all finished successfully. The patch also removes the RunTime from the the e-mail when summarizing whole array, since it doesn't make sense to specify just the RunTime of one of the tasks for this case. Patch also fixes when ARRAY_TASKS is specified, previously the mail notification for the master job task record included a range of ExitCodes for all the tasks. Since this option is not for summarizing, the patch makes it so only the range is shown when the option isn't specified. Bug 4539.
-
Morris Jette authored
Scheduling fix for changing node features without any NodeFeatures plugins. Bug 4577
-
- 06 Jan, 2018 1 commit
-
-
Marshall Garey authored
Bug 4329 Bug 4312
-
- 05 Jan, 2018 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
-