This changed in 17.11 where if the size was 0 we would return 0 which messes
up the perl api.

Bug 3644

jobs have a priority that is lower than the selected job. Previous logic
would permit other jobs with equal priority (no jobs with higher priority).

Bug 3650

circumstances.

array element per line.

Bug 3573

If the depend_list is NULL or has zero elements, the string should
be cleared as well.

Bug 3651.

The field needs to have its own copy, otherwise the pointer will
become invalid when xfree()'d by a separate array task.

Bug 3665.

So that it is the same max length as in src/common/env.c.

Used for explicitly laying out tasks on large CPU count nodes (e.g., KNL).

Bug 3675.

Improve job scheduling sort after sorting by priority we now sort by
submit time and then by job id.  We used to not consider submit time.  This
handles the case where the job_ids have rolled or we are doing federation
scheduling.

Bug 3524

If a task in a parallel job fails and it was launched with the
    --kill-on-bad-exit option then terminated the remaining tasks using the
    SIGCONT, SIGTERM and SIGKILL signals rather than just sending SIGKILL.

Sinfo command with support for federated clusters

Add sprio --local and --sibling options for use in federation of clusters.

Add sprio -p/--partition option to filter jobs by partition name.
Add partition name to job priority factor response message.

Modify backfill logic so that bf_max_job_user, bf_max_job_part and
    bf_max_job_user_part options can all be used independently of each other.

Add SchedulerParameters option of bf_max_job_user_part to specifiy the
    maximum number of jobs per user for any single partition. This differs from
    bf_max_job_user in that a separate counter is applied to each partition
    rather than having a single counter per user applied to all partitions.

The problem will be solved by using per-partition QOS and setting
MaxJobPer[User|Account] on that QOS.
bug 3668

This was a regression in commit 1967d512.

Bug 3650

Add SchedulerParameters option of bf_max_job_user_part to specifiy the
    maximum number of jobs per user for any single partition. This differs from
    bf_max_job_user in that a separate counter is applied to each partition
    rather than having a single counter per user applied to all partitions.

specify --with-pmix.

Bug 3597

This makes it so you can also specify %slurm_with_pmix in .rpmmacros to specify
a non-standard pmix installation.

About "MCSParameters=ondemand,noselect:groupA|groupB|groupC",
you can separate ondemand,noselect and groupA|groupB|groupC into 2
parameters like you want. The first part is common for mcs plugin and
the second part is only for mcs/group, so it could be logical to put them
into 2 different parameters.

Bug 3428

the slurmctld.

This reverts commit a662a226.

the slurmctld.

Prior security check only permitted root or the SlurmUser to update.

Bug 3631.

This introduced a race condition between RPC messages starting
to be processed ahead of the plugin init() calls completing.

This reverts commit 6e65b5cb.

Bug 3646.

Only happens in a SPANK plugin on the setenv() call.
dyn_spank_set_job_env() in unaffected, and needs the NULL value for proper
backwards-compatibility.

Bug 3503.

Add squeue --local and --sibling options to modify filtering of jobs on
    federated clusters.

Modify slurm_load_jobs() function to load job information from all clusters
    in a federation.

Fix double free issue from commit 3851f619

Same issue from fixed in a different spot with b19637bd.

Bug 3617

This reverts commit 8343365f.

Fix double free issue from commit 3851f619

Same issue from fixed in a different spot with b19637bd.

Bug 3617