The error was being triggered by logic to collect accounting
information starting and not being completed when testing to
start a node ping RPC. In other words, the logic wasn't testing
for the completion of one RPC against the start of that same
RPC, but against the start of a different RPC. This change
moves all of the timeout logic into the ping_nodes.c module
where we can make sure that the timing of different RPCs do
not get confused with each other.
bug 1190

slurmd was logging:
"Error reading step 2031886.0 memory limits" (with various job/step IDs)
because it was treating SLURM_SUCCESS as an error rather than SLURM_ERROR
bug 1589

Disable changes to GRES count while jobs are running on the node.
Previous logic could clear GRES count data and generate counter
underflow then when attemtping to deallocate the job's resources
(including future job terminations when computing when and where
pending jobs will start as part of backfill scheduling logic).
bug 1589

if many steps/jobs finish at once.

Bug 1587

switch/cray: If CR_PACK_NODES is configured, then set the environment
    variable "PMI_CRAY_NO_SMP_ENV=1"
bug 1585

gating rpcs.

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

added back into the system.

Bug 1578

Bug 1550

their own jobs.

Bug 1469

A non-administrator change to job priority will not be persistent except
for holding the job. User's wanting to change a job priority on a persistent
basis should reset it's "nice" value.
Without this change a user might lower a job's priority, but Slurm will
not lower it more based upon fair-share changes.

Bug 1469
Return values from void functions are unknown and were causing
list_for_each to short ciruit processing of the job list.

Fix for misleading job submit failure errors sent to users. Previous error
could indicate why specific nodes could not be used (e.g. too small memory)
when other nodes could be used, but were not for another reason.
bug 1537

Correct the job array specification parser to accept brackets in job array
expression (e.g. "123_[4,7-9]").
This patch superseeds patch 8d811201
bug 1552

The logic fails if there are commas in the brackets:
slurmctld: job_str_signal: 3 invalid job id 1593_[2,5-6]
Updated patch in next commit
bug 1552

RequeueExit and RequeueExitHold configuration parameters modified to accept
numeric ranges. For example "RequeueExit=1,2,3,4" and "RequeueExit=1-4" are
equivalent.
bug 1549

If SchedulerParameters value of bf_min_age_reserve is configured, then
a newly submitted job can start immediately even if there is a higher
priority non-runnable job which has been waiting for less time than
bf_min_age_reserve.

Start job allocation using lowest numbered sockets for block task
distribution for consistency with cyclic distribution.
bug 1540

block is set up to it's original state.