- 30 May, 2018 14 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
Value of 2113 is where it fits in with 17.11, so pin it here.
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Michael Hinton authored
-
Tim Wickberg authored
Caused by pthread_cancel cleanup by commit e5f03971 in 17.11.6. Bug 5181.
-
Tim Wickberg authored
The race condition was created in a7c8964e in 17.11.6 when removing the (unsafe) pthread_cancel code handling thread termination. Bug 5164
-
- 24 May, 2018 1 commit
-
-
Brian Christiansen authored
Commits f18390e8 and eed76f85 modified the stepd so that if the stepd encountered an unkillable step timeout that the stepd would just exit the stepd. If the stepd is a batch step then it would reply back to the controller with a non-zero exit code which will drain the node. But if an srun allocation/step were to get into the unkillable step code, the steps wouldn't let the waiting srun or controller know about the step going away -- leaving a hanging srun and job. This patch enables the stepd to notify the waiting sruns and the ctld of the stepd being done and drains the node for srun'ed alloction and/or steps. Bug 5164
-
- 21 May, 2018 1 commit
-
-
Dominik Bartkiewicz authored
g_qos_count, g_qos_max_priority, must be call under qos write lock. Bug 5159.
-
- 19 May, 2018 3 commits
-
-
Brian Christiansen authored
Display correct path.
-
Bjørn-Helge Mevik authored
Bug 5151
-
Michael Hinton authored
Gres logic was resulting in job submit failure for all jobs if no GRES configured bug 5191
-
- 18 May, 2018 8 commits
-
-
Brian Christiansen authored
Commits 4454316e and 76706b51 adjusted the updating of priority logic so that when a non-authorized user modifies the priority it will only be temporary -- in most cases the user will never see that change. Bug 5151
-
Marshall Garey authored
Clarification of c2c06468. Bug 5150
-
Tim Wickberg authored
-
Tim Wickberg authored
Locks are held already on entry to _fill_ctld_conf.
-
Tim Wickberg authored
_fill_ctld_conf() will call in here with only the job read lock. Calling get_next_job_id with test_only set to true is safe in that scenario.
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
- 17 May, 2018 1 commit
-
-
Danny Auble authored
PriorityFlags=ACCRUE_ALWAYS is set. Bug 5186
-
- 16 May, 2018 5 commits
-
-
Morris Jette authored
This corrects some logic from commit da8c8374 Coverity CID 185653
-
Morris Jette authored
This bug was introduced in commit 4a9bffe1 Test12.7 was resulting in the logging of error messages of this sort: sacct: error: slurmdb_ave_tres_usage: couldn't make tres_list from '' This was due to the tres_usage_in_ave and tres_usage_out_ave fields being empty ('\0') if the job's cpu count is zero, which makes calculation of averages impossible. bug 2782
-
Alejandro Sanchez authored
-
Alejandro Sanchez authored
Bug 5174.
-
Dan Barke authored
Since having 'nocreate' would override the following option: create 640 slurm root Bug 5174.
-
- 15 May, 2018 6 commits
-
-
Morris Jette authored
Add node_features plugin function "node_features_p_reboot_weight()" to return the node weight to be used for a compute node that requires reboot for use (e.g. to change the NUMA mode of a KNL node). Add NodeRebootWeight parameter to knl.conf configuration file.
-
Morris Jette authored
-
Morris Jette authored
If ReturnToService=2 is configured, the test could generate an error changing node state to resume after setting it to down. The reason is if the node communicates with slurmctld, then its state will automatically be changed from down to idle and resuming an idle node triggers an error.
-
Alejandro Sanchez authored
-
Alejandro Sanchez authored
Bug 5168.
-
Alejandro Sanchez authored
Previously the default paths continued to be tested even when new ones were requested. This had as a consequence that if any of the new paths was the same as any of the default ones (i.e. /usr or /usr/local), the configure script was incorrectly erroring out specifying that a version of PMIx was already found in a previous path. Bug 5168.
-
- 11 May, 2018 1 commit
-
-
Morris Jette authored
-