different times when reservations are using the associations that are
being deleted.

Remove logic that was creating GRES bitmap for node when not needed (only
needed when GRES mapped to specific files).

Correct logic to support job GRES specification over 31 bits (problem
in logic converting int to uint32_t).

when terminating the job.

different number of dimensions than the cluster.

when terminating the job.

--signal option.

to allow sview to display blocks correctly.

to avoid overlapping erroneously.

Before you could get overlapping reservations if you asked for a core
based reservation and then a whole node reservation.  This fixes that.

describing the error code.

Test 3.11 was failing in some configurations without this as
the CPU count in the RPC was lower than the number of nodes in
the required node list

MaxProcSecondsPerJob.

error

terminating a job.

and abort the job.

a midplane.

MaxNode limit.

only needs to be called once.

    reference.

s_p_options_t struct.

The CPU specification enforcement is strict rather than advisory.

warning.

of cpus in the job_resources_t structure so as nodes finish the correct
cpu count is displayed in the user tools.

Previous logic would only make available the CPUs associated with
the first N GRES, where N is the number of requested GRES. CPUs
which might be made available by using different GRES were not
considered available.
bug 1092