- 24 Jan, 2017 26 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Morris Jette authored
Some portions of tests 21.30 and 21.34 failed with accounting and priority basic. These changes disable portions of those tests as needed based upon configuration.
-
Tim Wickberg authored
FreeBSD requires this to build; overlooked in 2d9e999f.
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
Update information about modified functions and data structures.
-
Morris Jette authored
It was leaking memory otherwise
-
Dominik Bartkiewicz authored
_allocate_sc() is heavily used within the scheduler, change to stack allocation from heap to avoid constant churn on xmalloc()/xfree(). Bug 3420.
-
Morris Jette authored
-
Tim Wickberg authored
"can be taken out 2 versions past 15.08"... we're now three past. Unlink from build, remove and remove fallback call to it in sh5util.c.
-
Tim Wickberg authored
-
Isaac Hartung authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
test1.63 was failing periodically due to a race condition. A signal was being sent to srun before the signal handler thread was spawned.
-
Brian Christiansen authored
Too closely related to working_cluster_rec.
-
Brian Christiansen authored
CID 16088[1-4]
-
Tim Wickberg authored
-
Tim Wickberg authored
Could be used in bit_ffs and bit_fls functions rather than existing for loops.
-
Tim Wickberg authored
-
Tim Wickberg authored
-
- 23 Jan, 2017 14 commits
-
-
Tim Wickberg authored
-
Danny Auble authored
Bug 1599
-
Danny Auble authored
-
Morris Jette authored
Add new knl.conf parameter to the capmc_suspend and capmc_resume programs. They are not used by those programs, but we need to prevent an error if those new parameters are used.
-
Morris Jette authored
-
Morris Jette authored
Reset a job's memory limit based upon what's available after node reboot, which can change on a KNL if the MCDRAM mode is changes on reboot
-
Morris Jette authored
This bug was likely the root cause of bug 3366. If the backfill scheduler allocates resources for a batch job and a node reboot is required, the batch launch RPC would be sent to the agent. At that point, there is a race condition between the agent and the job_time_limit() function testing for boot completion. If the job_time_limit() function ran first, it would trigger a second launch RPC request getting sent to the agent. bug 3366
-
Morris Jette authored
Clean up logic to test if job is configuring bug 3366
-
Morris Jette authored
Do not launch a batch step while the job is configuring. Previous logic checked for the PrologSlurmctld running, but not nodes booting. Checking the job's CONFIGURING state flag will validate both. bug 3366
-
Morris Jette authored
Add check to avoid step allocation logic from executing job configuration completion logic multiple times (check if job is configurating before clearing flag and resetting time limit). bug 3366
-
Brian Christiansen authored
-
Morris Jette authored
slurmctld/agent race condition fix: Prevent job launch while PrologSlurmctld daemon is running or node boot in progress. bug 3366
-
Morris Jette authored
This is required to manage the configuration completion. bug 3366
-
Morris Jette authored
This will be required to lock the job structure bug 3366
-