Add new SchedulerParameter of permit_job_expansion to permit expansion of
running jobs.

Replace the two calls to select_g_job_expand_allow() as all plugins return
true anyways at this point. Return ESLURM_NOT_SUPPORTED instead of
ESLURM_DEPENDENCY in one location as well to provide a better error
message back to the user.

Bug 5716.

Changes saccct, squeue, sinfo, sprio so that -l and -o
are mutually exclusive.

Bug 6438

Bug 6441.

so that squeue -s and sstat will show the batch step, and sacct will
show the batch step before the job finishes.

Bug 6196.

The correct printf format for size_t is %zu not %lu.

Bug 6430

The code to handle it was already there, this just made it so we
actually parsed it.

Bug 6430

Commit 750cc23e changed the signature for slurm_xmalloc, which
needs to be mirrored here in slurm-perl.h.

Bug 6436.

Adds SPRIO_FORMAT env variable, which is equivalent to the
-o/--format option. Accounted for the new env var in the test suite.

6063

Force intermediate values to uint64_t to catch the potential overflow.

CVE-2019-6438.

The information will be logged for all tasks of a job array with
a task count limit.
bug 5093

On a heterogeneous system the gres.conf coming from various nodes
might not be complete.  The slurm.conf has a complete list of possible
gres on the other hand.

If the GRES doesn't exist we will print an error and use the id instead
of the name, but this should never happen.

Bug 6366

When trying to update the partition list of a job it didn't
get updated.

Bug 6329

Bug 6320

Bug 6004

specific tasks.

Bug 6357

Bug 6004

Update seff to reflect API change from rss_max to tres_usage_in_max. Use
Slurmdb::find_tres_count_in_string to parse out the TRES_MEM value.

Bug 6004

Bug 5736

This check really is there to test if we have dynamic(inactive) features.

Obviously this doesn't work on heterogeneous systems, but there is no
good way to check for this as this check is used long before nodes are
considered.

Bug 6242

Docs updated with details. 'node' is simply removed from the tres list;
the report will continue if other valid tres are specified.

Bug 5954

This adds the -b option to salloc, srun and sbatch
which is equal to --begin.

Bug 6356.

Bug 6356.

Fixed srun from double printing invalid option
msg twice. Also removed the unused -b flag from sbatch.

Bug 6356.

It has been shown in a couple of ways these 2 apis are dependent
on each other, but both export similar symbols, so when you link
to both of them you get duplicate symbols.

Bug 1394

Update the documentation, and split "classic" fair share details
off to a separate page.

Bug 6036.

scontrol and sview won't report Consumed Joules and Lowest Joules anymore.
The reason is that these values were collected from slurmd start time which
made them not useful for the users.

Bug 6283

This patch fixes the regression caused by 07483564 where only the
linux plugin was handling this scenario correctly.

Bug 6332

Bug 4700.

Co-authored-by: Tim Wickberg <tim@schedmd.com>

Bug 6331

This patch removes the MemLimitEnforce parameter from Slurm and moves the
condition to enable the feature to the JobAcctGatherParam=OverMemoryKill.
Setting OverMemoryKill will now enable the mechanism that was before enabled
with MemLimitEnforce=yes, so activation of killing jobs or steps due to
exceeding memory will be done in the same place. Also reconfiguring or
starting slurmd/ctld with incorrect configuration will cause a fatal error.

Bug 5479

Add a debug statement.

Bug 5823

When the backup slurmdbd is active, there is no need to print
connection errors every 10 minutes when the backup checks in on the
primary, at least at the 'error' level.

Prevent dbd clients, like sacctmgr, from printing a connection error
when running commands against the backup slurmdbd unless debug2.
Before, the clients would always print errors when trying to access
the primary dbd first.

Bug 5823

Support GRES types that include numbers (e.g. "--gres=gpu:123g:2").
Also change number suffix processing to use common function
See commit 396e82a167
bug 6345

Fix issue introduced in commit 164d4878 that avoided a job to be modified
setting the current reservation to none.

Bug 6309

which caused negative values and values starting with a decimal
to be invalid for PriorityWeightTRES and TRESBillingWeight.

Bug 6217

This is useful for testing and debugging.