configured.

fails to enter the desired NUMA and/or MCDRAM mode then drain the node and
requeue the job.

Bug 3785

prolog is ran after the reboot.

Bug 3618

Precursor for next commit.

Bug 3618

Bug 3695

bug 3779

If capmc reports a node name, but not mcdram_cfg for the node, then
  log the missing data rather than assume the value is zero and
  report a value mismatch with cnselect.

When requesting an operation on jobs, where the operation permits to specify
more than one job in the same request, and a job array appears before a
regular job (no-array job) in the list of jobs to operate with, the
job_array_resp_msg_t pointer was not properly NULL'ed and thus incorrectly
accessed when processing the no-array job. This fix prevents the crash from
happening in the following scontrol operations:

uhold, hold, suspend, requeue, requeuehold, update, release

when the same request has <array_jobid>,<non-array_jobid> in this order in
the job list to process.

Bug 3759

Job expansion example in FAQ enhanced to demonstrate operation in
    heterogeneous environments.
bug 2979

Do not attempt to schedule jobs after changing the power cap if there are
    already many active threads.

Bug 3760

didn't work at all.

Bug 3712.

This reverts commit ecfd007f.

It was noticed that while doing any update to a job the admin comment would
be blown away.  This patch fixes that.

Bug 3789

run multiple tasks on multiple nodes.  Changing the max nodes setting from
3 to 6 fixes the issue without apparent compromise to the test.

destroying a mutex.

Bug 3612

Looks like a regression in commit ad07aebc

clear it as started.

This reverts commit e87edf8d.

Per Moe's suggestion, we revert this sense it most likely isn't totally
correct.

select_g_select_nodeinfo_set().

This is a continuation of commit 80443cc1.

Bug 3690.

Test 1.62 will fail otherwise.

we failed.

Bug 3690 continuation of commit bf0429d1.

bf0429d1 this is no longer needed to wait as long.

Bug 3690 continuation of commit bf0429d1.

If this failed the job was 3/4's allocated and not in the database.

This would cause a segfault if done where it happened before.

Bug 3690 continuation of commit bf0429d1

The decay thread could signal the cond before the init thread waits for
it causing deadlock.

In order to test with larger systems, modify capmc script to generate
  output with arbitrary start and end NID values

Bug 3725

in general.

at shutdown. More likely to happen in the fed_mgr than the dbd since the
fed_mgr closes the persistent connections before they are signaled by
the persistent connection server.

pointer.

selected for a job.

Bug 3690