Bug 6501.

Bug 6791.

This prevents rebuilding a job's dependency string when it has at least
one invalid (never satisfied) dependency, no matter if such invalid
dependency has already been purged (after MinJobAge) or not. This can
be useful to track down the culprit invalid dependencies even after they
are gone from ctld's in-memory job list.

The flag is cleared upon a successful job dependency update or after
another job in the dependency list has been satisfied if such list is
composed with the '?' symbol (OR'ed).

Bug 5851.

Job dependencies separated by "?" (OR'ed) should make the dependant job
be independent as soon as any of the dependencies are resolved to be
satisfied. Without this patch, if an invalid (non satisfiable)
dependency was resolved before a satisfiable one, then the dependant job
would never become independent, even after the satisfiable one got
eventually resolved.

Bug 5851.

The response of the XCC raw command is always 16 bytes, we log it and return if
we don't get an answer of this size.

Bug 6743

If GRES configuration data is unavailable from gres.conf, then use the
    node's "Gres=" information slurm.conf. This will eliminate or minimize the
    gres.conf file in many situations.
bug 6761

In 0e149092 not setting the variable when job was not requesting any gres
was considered a bug. The cuda API will use all devices if the variable is
not set. If it is set to some unknown or empty value, it will use no devices.
This variable should be used only for testing purposes and ConstrainDevices=yes
in cgroup is recommended.

Bug 6412

gres plugins will setup environment for every gres in the system even if the
job has not requested it.

Bug 6412

Removed linear search, replaced with direct record references and a hashmap.
This is faster and avoids potential collisions between assoc id's and user id's.
Bug 4811

Bug 6750.

Bug 6710.

Change to %pJ identifier while here and merge different partition
priorities into a single log message line.

Bug 6663.

Bug 6605.

Bug 6723

Regression from enhancement 4506.

Bug 6680

Bug 6662

Previously the state reason could remain as WAIT_NO_REASON even after
backfill evaluation. This should improve system feedback/responsiveness
user perception.

Bug 6594.

Continuation of 69d78159

Bug 6500

Issue was from ade9101e.

The problem was an over simplified if statement which when ran multiple
times would set the start time incorrectly.

Bug 6697

Even if main scheduler doesn't allocate resources for hetjobs, the
queue list should be composed by all types of jobs. Otherwise, lower
priority regular jobs could be allocated resources by main scheduler
while higher priority hetjobs are waiting for a backfill cycle.

Bug 6593.

Bug 6708.

Bug 6679

This reverts commit 082c59dd.

Bug 6286

Instruct the backfill scheduler to attempt to start a heterogeneous job
as soon as all of its components are determined able to do so.

Bug 5579.

I neglected to add a pre4 section after tagging pre3.

There are at least two points where this can return a false positive
error message which can be confusing for users.

Continuation dc583bd1

Bug 6437

This used to be the short form for --account, but was changed to
-A ahead of the Slurm 2.1 release over nine years ago.

bug 6646

Backport of 21b9a39b

Bug 6625

Never called. None of the plugins have bothered to implement this correctly.
The jobcomp/script plugin comes closest, but did not pick error codes within
the designated range.

Bug 3647.

Leave the state file name - burst_buffer_cray_state alone.

Bug 6440.

Print error: for each new line.

Bug 6142

Bug 6142

Bug 6584