Bug 1446

don't insert a new row in the event table.

uid's are 0 when associations are loaded.

 Fix segfault in controller when deleting a user association of a user which had been previously removed from the system.

 Bug 1238

Fix slurmctld initialization problem which could cause requeue of the last
task in a job array to fail if executed prior to the slurmctld loading
the maximum size of a job array into a variable in the job_mgr.c module.

Fix slurmctld job recovery logic which could cause the last task in a job
array to be lost on restart.

event  REQUEUED to slurmdbd.

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.

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

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

bug 1379

bug 1375

What this does is use the core level binding after each task is laid out
to skip all the extra threads in the core so it doesn't give them to
another task.

It probably isn't perfect, but does solve all the scenarios I found.