of Slurm daemons.

The slurmstepd still needs to be fixed, which most likely can't be fixed
until 15.08.

of Slurm daemons.

and SLURM_JOB_RESERVATION in the batch job.

but then sets CPUs to only represent the number of cores on the node.

Bug 1327

doesn't request a number of tasks.

Fix job array hash table bug, could result in slurmctld infinite loop or
invalid memory reference.
bug 1309

If a master job array record is complete, then consider all pending
tasks as also complete. This problem happens when a master job array
record is pending (has pending tasks) and is cancelled. The result
previously was a job record not visible to squeue/scontrol, but occupying
memory.
The same type of problem happened with respect to a dependency on a job
array which was cancelled.

If a QOS was added for the job and then removed and it just happened
to be the largest QOS id wise if the slurmctld was restarted and the job
wasn't flushed out yet it could mess things up.

Log how many nodes are removed from consideration from jobs due to
  advanced reservation.
Change user error message to indicated that required nodes might
  be down, drained or (added this bit) reserved.

In proctrack/linuxproc and proctrack/pgid, check the result of strtol()
for error condition rather than errno, which might have a vestigial error
code.

correctly.

accounting_storage/filetxt.

The task_dist_states variable has been split into "flags" and "base"
components. Added SLURM_DIST_PACK_NODES and SLURM_DIST_NO_PACK_NODES values
to give user greater control over task distribution. The srun --dist options
has been modified to accept a "Pack" and "NoPack" option. These options can
be used to override the CR_PACK_NODE configuration option.

to have all the limits a QOS has.  If a limit is set in both QOS
the partition QOS will override the job's QOS unless the job's QOS has the
'PartitionQOS' flag set.

when running from cache.

Bug 1305

Fix bug with GRES having multiple types that can cause slurmctld abort.
This can be reproduced with select/cons_res and one Gres like this:
Name=gpu Type=kepler File=/dev/tty0
A bad index was being used that caused an assert.

Logic introdiced in version 14.03.10 to support requeueing of jobs
with GRES allocated to currently running steps broke select/linear
due to differernces in the plugin logic. The commit with the bad
logic is 1209a664

Bug 1298

Bug 1301

have no weight.  This allows for association and QOS decay limits to work.

Before without this option accounting would not be correct unless the
job was allocating enough resources to fill up the socket.  Making this
the default makes it so the entire socket is allocated to job similar to
the way CR_CORE works with allocating the entire core to the job even if
they don't allocate the whole core.

draining  in sinfo output.

Fix jobs from starting in overlapping reservations that won't finish before a "maint" reservation begins.

Bug 1290

Avoid huge malloc if GRES configured with "Type" and huge "Count".

when the DBD is down.