- 09 Jan, 2018 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
Used by new node features development
-
- 08 Jan, 2018 6 commits
-
-
Morris Jette authored
-
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
-
- 07 Jan, 2018 1 commit
-
-
Brian Christiansen authored
695d33b8 removed the REQUEST_SIGNAL_TASK_GLOBAL case statement which was the only case statement that didn't set an use the rc = SLURM_SUCCESS.
-
- 06 Jan, 2018 1 commit
-
-
Marshall Garey authored
Bug 4329 Bug 4312
-
- 05 Jan, 2018 14 commits
-
-
Marshall Garey authored
Bug 4448
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Brian Christiansen authored
-
Felip Moll authored
Avoid setting node in COMPLETING state indefinitely if the job initiating the node reboot is cancelled while the reboot in in progress. Bug introduced in commit 7d246784 Bug 4536
-
Brian Christiansen authored
Bug 4448
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
# Conflicts: # NEWS
-
Danny Auble authored
-
Danny Auble authored
-
Alejandro Sanchez authored
Updated also some link references as agreed by e-mail with R. Castain. Continuation of bbfd1890.
-
- 04 Jan, 2018 16 commits
-
-
Danny Auble authored
-
Morris Jette authored
This should have been part of commit 75f0789d bug 4531
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
bug 4575
-
Danny Auble authored
Update slurm.spec and slurm.spec-legacy as well
-
Dominik Bartkiewicz authored
Add job state flag of "SIGNALLING" to avoid race condition with multiple SIGSTOP/SIGCONT signals for the same job being active at the same time. bug 4531
-
Marshall Garey authored
Logic was backwards before. Bug 4459.
-
Morris Jette authored
-
Morris Jette authored
These tests were failing on a single node cluster
-
Isaac Hartung authored
-
Danny Auble authored
-
Morris Jette authored
-
Jeff Frey authored
Refactor logging logic to avoid possible memory corruption on non-x86 architectures. bug 4469
-
Alejandro Sanchez authored
There are out of memory conditions where spikes of memory usage hit the limit set. When this happens (failcnt > 0), the Kernel might be able to reclaim unused pages and the process can continue without oom-killer actually killing the process. This may or may not result in an app problem, thus we want to better clarify the message. A separate bug will track the potential addition of a new feature to better discern memory limits being hit from oom-killer actually killing the process. There are mechanisms to register a notifier through the cgroup.event_control control file, so that the application can be notified through eventfd when OOM-Killer actually kills the process. Bug 3820.
-
Alejandro Sanchez authored
Link published to the slurm-users list by Ralph Castain: https://pmix.github.io/pmix/how-to
-