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.

Fix for GRES scheduling in which there is CPU topology defined or
GRES types defined and there is more than 1 GPU per topology record
in slurmctld. Without this fix, only one GRES could be allocated
from each defined topology.
bug 1369

The slurmctld could abort with a gres configuration having
Type= configured, but no CPU binding configured.

Most of these don't matter as they are all NO_LOCK

Fallout from commit f1ebdef1 when the resources were added.

Intel MPI, on MPI jobs initialisation through PMI, uses to call PMI_KVS_Put()
many many times from task at rank 0, and each on these call is followed by
PMI_KVS_Commit(). Slurm implementation of PMI_KVS_Commit() imposes a delay
to avoid DDOS on original srun. This delay is proportional to the total number.
It could be up to 3 secs for large jobs for ex. with 7168 tasks. Therefore,
when Intel MPI calls PMI_KVS_Commit() 475 times (mesured on a test case) from
task at rank 0, 28 minutes are spent in delay function.
All other tasks in the job are waiting for a PMI_Barrier. Therefore, there is
no risk for a DDOS from this single task 0. The patch alters the delaying time
calculation to make sure task at rank 0 will does not be delayed. All other
tasks are globally spreaded in the same time range as before.

Fix race condition that could start a job that is dependent upon a job array
before all tasks of that job array complete.
bug 1324

Bug 1350

flag from a job while the job is waiting for a block to boot.

Bug 1346

a normal job.

Prevent invalid job array task ID value if a task is started using gang
scheduling (i.e. the task starts in a SUSPENDED state). The task ID gets
set to NO_VAL and the task string is also cleared.