- 06 Sep, 2018 2 commits
-
-
Morris Jette authored
Bug 5672 Coverity CID 164845
-
Danny Auble authored
Bug 5529 Seconded by Moe.
-
- 05 Sep, 2018 1 commit
-
-
Danny Auble authored
LaunchParameters=send_gids. Bug 5620
-
- 04 Sep, 2018 4 commits
-
-
Morris Jette authored
Bug 5659
-
Danny Auble authored
This reverts commit 35285e40.
-
Danny Auble authored
Bug 5659
-
Morris Jette authored
Bug 5663
-
- 31 Aug, 2018 3 commits
-
-
Marshall Garey authored
Spaces need to be built into each key definition, otherwise it'll all run together. Bug 5657.
-
Tim Wickberg authored
Otherwise assoc_mgr_fill_in_user() will abort on a failed lock annotation. Convert to designated initializer format while fixing this. Bug 5653.
-
Tim Wickberg authored
Move the trigger_backup_ctld_fail() call into ping_controllers(), and use the ping_all boolean as a standin for whether we're the active controller or not. Bug 5256.
-
- 30 Aug, 2018 8 commits
-
-
Tim Wickberg authored
Bug 5651.
-
Tim Wickberg authored
-
Tim Wickberg authored
Will be needed to distinguish between which backup controller is resuming. Bug 5256.
-
Tim Wickberg authored
This should solve a clang/scan-build issue. Bug 5256.
-
Dominik Bartkiewicz authored
starting. Bug 5565
-
Morris Jette authored
-
Danny Auble authored
Bug 5623
-
Danny Auble authored
%n or %h in the spool dir. Bug 5096
-
- 29 Aug, 2018 4 commits
-
-
Brian Christiansen authored
By default all devices are allowed and GRES, that are associated with a device file, that are not requested are restricted. Leaving the ability to read in the file as a contribution is under review that extends the cgroup_allowed_devices_file. Bug 4771.
-
Dominik Bartkiewicz authored
Fail early when the layout requirements cannot be satisfied in _task_layout_lllp_block(). Otherwise step layout calculations will fail, leading to a "fatal: _task_layout_lllp_block infinite loop" Bug 5415.
-
Dominik Bartkiewicz authored
The conditional for handling --overcommit was not sufficient to prevent other option combinations from using that code path, resulting in unexpected resource allocation behavior. Correct that to check that overcommit is enabled. Bug 5345.
-
Dominik Bartkiewicz authored
This does change a network RPC after 18.08.0rc1, which is best to be avoided. But other recent changes have already broken RPC compatibility between what will be 18.08.0, so we might as well land this now. Bug 5443.
-
- 28 Aug, 2018 1 commit
-
-
Marshall Garey authored
Bug 5524 Basically count was never getting over 3 so none of the "end" code was ever happening.
-
- 27 Aug, 2018 2 commits
-
-
Danny Auble authored
running. Bug 5624
-
Dominik Bartkiewicz authored
for an allocation. Bug 5293 Backport of 9a507584 in 18.08.
-
- 24 Aug, 2018 1 commit
-
-
Broderick Gardner authored
return a start and end time set to the window end time, so elapsed time is 0. Bug 5372
-
- 23 Aug, 2018 3 commits
-
-
Danny Auble authored
Bug 5619 Tim approved
-
Danny Auble authored
Bug 5618
-
Tim Wickberg authored
Development continues on the master branch for 19.05, but the snapshot here should not be used and is thus being removed. Remove the commented-out documentation as well.
-
- 22 Aug, 2018 4 commits
-
-
Danny Auble authored
Bug 5608 Tim approved
-
Brian Christiansen authored
If the dbd comes up after a job array has been submitted to the controller, the controller calls _update_job_tres() which calls assoc_mgr_set_tres_cnt_array() which allocates memory for the job's tres_alloc_cnt. The job array gets scheduled, but job_array_split() doesn't NULL out the pending job's tres_alloc_cnt, so both the array task and the pending array job are pointing to the same memory. The array task calls job_set_alloc_tres() which free's the running job's tres_alloc_cnt and now the pending array job is pointing to bad memory and when the array splits again the new array task tries to free tres_alloc_cnt in job_set_alloc_tres() and segfaults. Bug 5604
-
Tim Wickberg authored
-
Danny Auble authored
-
- 21 Aug, 2018 7 commits
-
-
Danny Auble authored
-
Felip Moll authored
Bug 5538
-
Danny Auble authored
Bug 5538 This will be handled further in bug 5602
-
Isaac Hartung authored
Previous behavior was confusing, and the code path hard to follow. Rework, and clarify the established behavior in the appropriate man pages. Bug 4514.
-
Broderick Gardner authored
X11 implies Contain, and Contain is incompatible with NoHold as the Extern step creation will race with the step launches. Bug 5500.
-
Dominik Bartkiewicz authored
Bug 5166
-
Tim Wickberg authored
Bug 5426
-