Bug 6807.

Bug 6807.

Updated ControlAddr to point to 127.0.0.1 rather than 123.4.5.6

Bug 6794

Bug 6768.

Bug 6718.

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.

No functional change, just preparement for a following commit with an
actual fix.

Bug 5851.

Continuation of 2764f3fd

Bug 6589

Continuation of 9a243a1a

Bug 6592

Bug 6750.

Bug 6710.

Bug 6590.

Bug 6680

With schedulerparameters=defer and prolog scripts and/or spank plugins
that take some time, jobs weren't starting within 2 seconds that tests
2.18 and 2.19 expected, causing these tests to fail.

Bug 6670.

IMO, the test as is currently designed is not representative of
an actual rpmbuild against a production released tarball, and thus
should not be relied on. Using --nodeps masks a lot of potential
errors with the spec file.

It has been disabled on Ubuntu systems for months, broken on master
for longer, and thus I am discarding it now.

Bug 4411, 6281.

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

Bug 6663.

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 6679

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.

This could probably be extended to give back sockets and cores and
such, but at this moment I really only needed how many threads to deal
with and total cpus.

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

Bug 6658

Bug 6658