to send user signal at preemption time.

Bug 5867

to send job warn signal. In the gracetime logic, it wasn't checking for
the B option.

Bug 5867

# Conflicts:
#	src/slurmctld/acct_policy.c
#	testsuite/expect/README
#	testsuite/expect/globals
#	testsuite/expect/test21.39

Bug 6625.

Also correction to rebase problem
Bug 6635

Change order and wording of FS=1 error.
Print out what the system detects when there is a FS=1 discrepancy.
Create sub-tests testing FS=1.

Bug 6635

These are conditions that need to remain constant until something
changes on the job to reevaluate.

Bug 6625

What was happening here is you had to not be >= operator to have the old
limits removed.  This makes it so it always happens.

Bug 6625

Bug 6625

Before we went up the tree to the next assoc_ptr.  As we validate an
association on the id as well as the uid the assoc_ptr was eventually
going to become invalid.  Setting it to NULL here solves a bunch of
issues with things later on.

Bug 6625

Bug 6625

Bug 6625.

Don't abort when the job doesn't have an association that was removed before the job was able to make it to the database.

Bug 6625

Bug 6635

Convert fast_schedule from global to function parameter.
Clarify and improve comments.
Fix error involving expect processing if matching both errors and
output.

Bug 6635

Add debug2 print statement for fastschedule=1.
Remove "_" syntax from fake_gpus.conf file (no need for it).
Fix test39.18 sub-test 0.4 to test for empty files and sorting.

Bug 6635

Move defines above function.
Remove TODO comment.

Bug 6635

Clarify NVML-related sub-tests.
Add message indicating convenient test feature.

Clarify function description comments.
Change a fatal to xassert, since it's really a development check.
Add a fatal if NVML happens to give us an empty CPU affinity array.
Update test 38.19 sub-test 0.14 to expect this fatal (in test prog).

Bug 6635

Bug 6625

As tmp and the underlying wait_all_nodes fields are unsigned this
can never be negative.

CID 197666.

CID 197667.

CID 197668.

CID 197670.

Do not set job's per-node minimum memory on error
Bug 5562 Comment 27

This reworks all CLI option parsing for salloc/sbatch/srun into a central
set of functions. This is designed to allow a future set of commits to
inspect, and potentially modify or unset, the set of options as specified
by the user through a consistent string based set of functions.

Bug 3745.

Invalid --cpu-freq options now cause srun to exit(-1), rather than
continuing with the job submission. The test had been designed to
assume the job would still be submitted, so modify it to match
the new stricter parsing.

Have slurm_process_option() call exit(-1) on errors. Most parsing
functions will already do this, but that should be revisited at a
later point in time.

Remove the options argument now that no calling paths need it.

Note that opt_string here is alphabetical *by the option name*,
and not by the val any longer.

Move handling for parallel debugging into _opt_verify(), and
explicitly call through slurm_process_option() to override the
default settings.