Will be needed to distinguish between which backup controller is resuming.

Bug 5256.

This should solve a clang/scan-build issue.

Bug 5256.

starting.

Bug 5565

Bug 5623

%n or %h in the spool dir.

Bug 5096

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.

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.

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.

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.

Bug 5524

Basically count was never getting over 3 so none of the "end" code
was ever happening.

running.

Bug 5624

for an allocation.

Bug 5293

Backport of 9a507584 in 18.08.

return a start and end time set to the window end time, so elapsed
time is 0.

Bug 5372

Bug 5619

Tim approved

Bug 5618

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.

Bug 5608

Tim approved

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

Bug 5538

Bug 5538

This will be handled further in bug 5602

Previous behavior was confusing, and the code path hard to follow.
Rework, and clarify the established behavior in the appropriate man pages.

Bug 4514.

X11 implies Contain, and Contain is incompatible with NoHold as
the Extern step creation will race with the step launches.

Bug 5500.

Bug 5166

Bug 5426

Bug 5072

MySQL permits up to 64-character database names, but Slurm was truncating
at 33-characters. If we exceed this limit, let the mysql_query fail and
give the admin a chance to sort it out, rather than truncating and then
failing to query against the un-truncated name later on.

While here correct the fatal() message.

Bug 5586.

Bug 5554

Currently only valid nextstate states are down and resume/idle so the
node shouldn't be in a drain state after transitioning into either of
these states.

Bug 5544

plugin.

Bug 5583

(i.e. gres=gpu/tesla) it would get a count of 0.

Note that pipe2() is Linux-specific, but this whole cgroup plugin is
already Linux-specific in design, and the eventfd() call itself is
Linux-specific as well.

Bug 5570.

Turns out if you don't close up everything you open the hdf5 lib doesn't
like that.

Fixs regression in 011b2f23.

Alphabetize target list while here.