Avoid placing pending jobs in AdminHold state due to backfill scheduler
interactions with advanced reservation.
Specifically, if the backfill scheduler tests a pending job can be
scheduled after it's advanced reservation ends then the job was
assigned a priority of zero (AdminHold).

undefined variable.

requested and allocated.

allocation as taking up the entire node instead of just part of the node
allocated.  And always enforce exclusive on a step request.

to attempt to signal tasks on the frontend node.

deny the job instead of holding it.

Fix for bug 268

to implicitly create full system block.

cpu count would be reflected correctly.

APRUN_DEFAULT_MEMORY env var for aprun.  This scenario will not display
the option when used with --launch-cmd.

per cpu.

If task count specified, but no tasks-per-node, then set the tasks
per node in the BASIL reservation request.

as the hosts given.

isn't a sub-block job.

the XML.

Fix for bug 258

never looked at to determine eligibility of backfillable job.

and when reading in state from DB2 we find a block that can't be created.
You can now do a clean start to rid the bad block.

the slurmctld there were software errors on some nodes.

without it still existing there.  This is extremely rare.

a pending job on it we don't kill the job.

while it was free cnodes would go into software error and kill the job.

Fix for bug 224

WIthout this patch, when the slurmd cold starts or slurmstepd
terminates abnormally, the job script file can be left around.
bug 243