Only if ALL of their partitions are hidden will a job be hidden by default.
bug 812

Correct SelectTypeParameters=CR_LLN with job selecition of specific nodes.
Previous logic would in most instances allocate resources on all nodes
to the job.

Correct squeue's job node and CPU counts for requeued jobs.
Previously, when a job was requeued, its CPU count reported
was that of the previous execution. When combined with the
--ntasks-per-node option, squeue would compute the expected
node count. If the --exclusive option is also used, the node
count reported by squeue could be off by a large margin (e.g.
"sbatch --exclusive --ntasks-per-node=1 -N1 .." on requeue
would use the number of CPUs on the allocated node to recompute
the expected node count).
bug 756

jobacct_gather/cgroup.

Support SLURM_CONF path which does not have "slurm.conf" as the file name.
bug 803

If a job has non-responding node, retry job step create rather than
returning with DOWN node error.
bug 734

Also correct related documentation

Completing nodes is removed when calling _try_sched() for a job, which
is the case in select_nodes(). If _try_sched() thinks the job can run
now but select_nodes() returns ESLURM_NODES_BUSY, the backfill loop will
be ended.

Fix sinfo -R to print each down/drained node once, rather than once per
partition. This was broken in the sinfo change to process each partition's
information in a separate pthread.

Correct sinfo --sort fields to match documentation: E => Reason,
H -> Reason Time (new), R -> Partition Name, u/U -> Reason user (new)

Without this patch, jobs with an infinite time limit would have
their preemption GraceTime ignored.

related to bug 789

them.

In slurm.spec file, replace "Requires cray-MySQL-devel-enterprise" with
"Requires mysql-devel" per David Gloe.

Related to bug 771

In version 14.03.2 was using "slurm_<jobid>_4294967294.out" due to
error in job array logic.

cnode counts.

This is for bug 775

regression from 2a674aee

is running.

together.

Switch/nrt - Properly track usage of CAU and RDMA resources with multiple
tasks per compute node. Previous logic would allocate resources once per
task and then deallocate once per node, leaking CMA and RDMA resources
and preventing their use by future jobs.

If a job is held, then only release it with the "scontrol release <jobid>"
command rather than a simple reset of the job's priority. This is needed to
support job arrays better. Otherwise a priority reset of a job array
would free all requeued/held jobs from that job array rather than
leaving them held.

in 2.0 :)