Previously it was not possible to distinguish between a job needing
exclusive nodes and the default job/partition configuration.

Fix job array logic that can cause slurmctld to abort.
bug 1426

Enable CUDA v7.0+ use with a Slurm configuration of TaskPlugin=task/cgroup
ConstrainDevices=yes (in cgroup.conf). With that configuration
CUDA_VISIBLE_DEVICES will start at 0 rather than the device number.
bug 1421

debug2 instead of info.

SLURM_JOB_PARTITION to be the one in which the job started.

If using proctrack/cgroup and gres/gpu, always start CUDA_VISIBLE_DEVICES
environment variable numbering at 0.
bug 1421

reservations.

This is an add on to commit 2e5142ef.  Servicing Bug 1418.

the partition in which the job runs.

Front End systems.

initially been added.

Project seems to be defunct. Last update March 2009.
http://xcpu.sourceforge.net/

Bug 1397

Bug 1384

If some tasks of a job array are runnable and the meta-job array
record is not runable (e.g. held), the old logic could start a
runable task then try to start the non-runable meta-job, discover
it can not run, and set its reason to "BadConstraints".

Test case:
Make it so no jobs can start (partition stopped, slurmd down, etc.)
submit a job array
hold the job array
release the first two tasks of the job array
Make it so jobs can start

Squeue modified to not merge tasks of a job array if their wait reasons
differ.
bug 1388

No functions currently exist, only the plugin wrapper and stubbed functions.

--export sbatch/srun command line option, propagate the users'
environ to the execution side. #1367

Interpret a partition configuration of "Nodes=ALL" in slurm.conf as
including all nodes defined in the cluster.
but 1382

bug 1379