- 30 Oct, 2015 2 commits
-
-
Morris Jette authored
-
Deric Sullivan authored
Fix creation of advanced reservation of cores on nodes which are DOWN. There seems to be a bug with reservations using a node list (e.g. Nodes=something + CoreCnt=something). The result is a reservation made that's arguably broken; listing the reservation (scontrol show reservation) will show "Nodes=" (blank) and "CoreCnt=0". It's very easy to reproduce, just by doing the following against a node in a DOWN (also tested with POWER_UP) state: scontrol create ReservationName=tmp_res StartTime=now EndTime=now+600 Nodes=<some_non_idle_node> CoreCnt=1 Users=<some_valid_user> scontrol show reservation. bug 2078
-
- 29 Oct, 2015 5 commits
-
-
Morris Jette authored
Better identify who can create and destroy persistent burst buffers.
-
Danny Auble authored
-
Danny Auble authored
submit_time. 0 means the job isn't eligible yet so we need to treat it so.
-
Danny Auble authored
-
Morris Jette authored
PrologFlags work: Setting a flag of "Contain" implicitly sets the "Alloc" flag. Fix code path which could prevent execution of the Prolog when the "Alloc" or "Contain" flag were set. bug 2074
-
- 28 Oct, 2015 3 commits
-
-
Morris Jette authored
If a user tries to create/destroy a persistent burst buffer and that is disabled (the default), return a permission denied error rather than an invalid request error. cray bug 832678
-
David Bigagli authored
-
Tim Wickberg authored
Bug 2071
-
- 27 Oct, 2015 15 commits
-
-
Danny Auble authored
-
Morris Jette authored
Log the minimum and maximum exit code (or signal) and show the state as "Mixed" if there are multiple termination states (e.g. cancelled, exit 0, exit 1, SIGBUS, etc.) bug 2058
-
Morris Jette authored
No change to logic
-
Danny Auble authored
it needed to check for INFINITE64 instead of zero.
-
Kevin Hildebrand authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
This just removes xfrees where the xfree had already happened.
-
Morris Jette authored
Correct scheduling logic for job features option with XOR construct that could delay a job's initiation. Some configurations and states with job feature XOR construct could prevent the job allocation from being made. bug 1865
-
Morris Jette authored
No changes to logic
-
Morris Jette authored
Improve sched/backfill support for job features, especially XOR construct. bug 1865
-
David Bigagli authored
-
David Bigagli authored
-
David Bigagli authored
-
- 26 Oct, 2015 9 commits
-
-
Tim Wickberg authored
-
Brian Christiansen authored
Bug 1973
-
Danny Auble authored
in the plugins.
-
Danny Auble authored
-
Danny Auble authored
when a user doesn't exist in the database.
-
Danny Auble authored
manager.
-
David Bigagli authored
-
David Bigagli authored
-
David Bigagli authored
-
- 24 Oct, 2015 3 commits
-
-
Morris Jette authored
Squeue recombines pending job array records only if their name and partition are identical. bug 2057
-
Brian Christiansen authored
AllocTRES and ReqTRES are the real mccoys.
-
Morris Jette authored
Job array termination status email ExitCode based upon highest exit code from any task in the job array rather than the last task. bug 2058
-
- 23 Oct, 2015 3 commits
-
-
Morris Jette authored
3 problems addressed: priority/basic does not currently support some functionality a test was assuming more than one node when submitting two jobs with the --exclusive optiion a sleep was required so that completing jobs could be cleaned up before submitting a subsequent job with the --immediate option
-
Danny Auble authored
-
Morris Jette authored
-