lots of jobs.

did the ALPS reservation.  Bug 1115

Take more job options into consideration to estimate its node count.

At work in Sweden we often fika (coffee+buns and what have u) at 3PM. I sometimes accidentally give a start time of 'teatime', so when I return from 'fika' I see my job's just getting started. This fix should make life even easier for the Swedes.

a reservation.

which they have access to (rather then preventing them from seeing ANY
reservation).  Backport from 14.11 commit 77c2bd25.

arbitrary layouts (test1.59).

option (since it isn't).

Do not cause it to be rebooted (powered up).

When a node's state is set to power_down, then execute SuspendProgram
even if previously executed for that node.

Fix logic determining when job configuration (i.e. running node power up
logic) is complete. (Will look at better solution for v14.11).

When a node's state is set to power_up, then execute ResumeProgram even if
previously executed for that node.

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.