- 23 Aug, 2018 7 commits
-
-
Tim Wickberg authored
Throw away all but the NEWS entry.
-
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.
-
Tim Wickberg authored
-
Morris Jette authored
This error occurs when one job is used to expand the allocation of another job. The node record's "run_job_cnt" is decremented when the dependent job's epilog completes and the job getting those resources never has the "run_job_cnt" updated for it, which later results in the "comp_job_cnt" underflow when it ends. This bug was discovered in the course of select/cons_tres development, but impacts all select plugins.
-
Yu Watanabe authored
-
Morris Jette authored
when a batch job gets resized to 0 nodes, it instantly gets killed, leaving resize scripts around. Also on a Cray system, the resize can not happen while the job step NHC is still active. This patch fixes both issues
-
Morris Jette authored
-
- 22 Aug, 2018 12 commits
-
-
Morris Jette authored
Coverity CID 187784 and 187785
-
Morris Jette authored
Coverity CID 187782
-
Danny Auble authored
# Conflicts: # NEWS
-
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
-
Morris Jette authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well.
-
Tim Wickberg authored
-
Danny Auble authored
-
Danny Auble authored
This will need to be revisited perhaps link to libslurmfull.so instead since we will need symbols not exported. See bug 5605
-
- 21 Aug, 2018 21 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Danny Auble authored
The previous commit causes erroneous errors to be printed. test2.14 was made a victim of it.
-
Danny Auble authored
# Conflicts: # src/plugins/jobacct_gather/common/common_jag.c
-
Danny Auble authored
-
Alejandro Sanchez authored
Bug 5561.
-
Felip Moll authored
Bug 5538
-
Danny Auble authored
Bug 5538 This will be handled further in bug 5602
-
Brian Christiansen authored
-
Brian Christiansen authored
Continuation of 27bf7328
-
Tim Wickberg authored
-
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.
-
Tim Wickberg authored
-
Tim Wickberg authored
This reverts commit dcc93022.
-
Tim Wickberg authored
-
Tim Wickberg authored
This reverts commit b9fb67d8.
-
Tim Wickberg authored
-
Morris Jette authored
CID 187777. Bug 5593.
-
Tim Wickberg authored
-
Tim Wickberg authored
scan-build complains about this possibly being used uninitialized with pthread_join(), but on review the path it identifies as causing that is impossible. Initialize this anyways in the hopes of surppressing that warning.
-