Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423

Fix to work with change logic introduced in Slurm version 2.6.3
scheduling logic which prevented Maui/Moab from starting jobs.

Add support for -W block=true	(wait for job completion)
Clear PBS_NODEFILE environment variable
Credit to NCSC

Add support for dependencies of job array elements (e.g.
"sbatch --depend=afterok:123_4 ..."). This does not support
depenendencies of ALL job array elements, only individual job
array elements.

preforms the allocation, regression in 2.6.3.

Previously the SlurmdDebug value in slurm.conf was ignored if the
previous value was not 3/init

This avoids building hostlist information with NodeHostName and
NodeAddr information unless explisitly requested and can improve
performance for the default mode of operation by about 65%.

Correct sbatch documentation and job_submit/pbs plugin "%j" is job ID,
not "%J" (which is job_id.step_id).

Without this change a job with a reason of WAIT_PART_DOWN,
WAIT_PART_INACTIVE, WAIT_PART_NODE_LIMIT, WAIT_PART_TIME_LIMIT, or
WAIT_QOS_THRES would not be cleared when that reason no longer
applied.

Add cgroup create retry logic in case one step is starting at the
same time as another step is ending and the logic to create
and delete cgroups overlaps.
bug 447

If a node has GRES and multiple threads per core the select/cons_res
plugin can get stuck in an infinite loop.
See bug 475
Contributed by:
PREVOST Ludovic
NEC HPC Europe

Previously a node failure would always requeue the job

Restore default behavior of allocating cores to jobs on a cyclic basis
across the sockets unless SelectTypeParameters=CR_CORE_DEFAULT_DIST_BLOCK
or user specifies other distribution options.
Reverts commit 7fcdc7e5
bug 466

If the backfill scheduler relinquishes locks and the normal job
scheduler starts a job that the backfill scheduler was actively
working, the backfill scheduler will try to re-schedule that
same job, possibly resulting in an invalid memory reference
or other badness.

Fix for --cpu_bind=map_cpu/mask_cpu/map_ldom/mask_ldom plus
--mem_bind=map_mem/mask_mem options, broken in 2.6.2.
See commit 718382da

The pending jobs will have their reservation info removed
bug 455

Initiate jobs pending to run in a reservation as soon as the reservation
becomes active.
Partial fix for bug 455

Revert commit 626be3ea
It was causing stack overflow and memory corruption

Previous logic only reported un-reserved node map.
New logging adds information about each job testing and where/when
it is scheduled resources.

slurm.conf when using the DBD.

Induced by bf_continue option and deleting a partition.

to reflect only the latest supported format.

if bf_continue option is configured and slurm is reconfigured during
one of the sleep cycles, then the backfill scheduler will reference
an invalid partition pointer.

Previous logic would place more tasks on each node than specified
by --ntasks-per-node, using fewer nodes than desired. This only
happens with exclusive node allocations (e.g. in partition
configuration Shared=Exclusive).