you query against that with -N and -E you will get all jobs during that
time instead of only the ones running on -N.

Signed-off-by: Danny Auble <da@schedmd.com>

to a list, which can be arbitrary size

was already in error and isn't deallocating and underlying hardware goes
bad one could get overlapping blocks in error making the code assert when
a new job request comes in.

overcommit.

overcommit.

Previously only requeued the job once

Without this change, the nodes associated with a reservation would
only be updated if the partition's nodes were reset using the
"scontrol update partition" command, but not if they were reset
using "scontrol reconfigure"

written by other cpus sharing the package

where needed)

This reverts most of commit
https://github.com/SchedMD/slurm/commit/570941362ffdc57e9e3d4723bc4f728ae04789d8
and adds a call from slurmctld to srun prior to deallocating nodes and
notifying slurmd to cancel the tasks

Otherwise an aborted slurmstepd can cause the srun process to hang
indefinitely; a problem reported in trouble ticket 149.

If the slurmstepd connects task I/O, but aborts after srun accepts the connect
and before slurmstepd writes data then srun could possibly hand indefinitely.
This probably does not explain failures seen at CEA, but can't hurt matters.
then the sr

This could happen in srun too and would typically indicate that
the munged is too busy to respond