bug 7197

Fix for test 21.39. If the job didn't start running before the
account/qos was removed, then the job would never start running, and the
test would fail.

Bug 6942.

Previous logic could hang indefinitely if srun did not return
It also performed unneeded test setup before confirming that the
system size was adequate to execute the test.

bug 7050

Remove excess tabs to properly align code
Make comment formats consistent

No functional changes.

Bug 7050.

Bug 7050.

Bug 7050.

Handles cases where last line of slurm.conf is not empty.

Bug 7050.

One part of this test can fail in a heterogeneous system. Do not run the
part of the test that would fail if the system is heterogeneous.

Bug 7051.

JobHeldUser state reason was properly set for user held jobs during the
course of job_allocate() execution until calling _select_nodes_parts()
which could override it under certain conditions (i.e. when accounting
policy limit is hit). The fix restores it back when appropriate.

Continuation of 8712a254.

Bug 7136.

backport test7.20 changes from master to v18.08.

bug 7050

Bug 7146.

No functional changes to fsync_and_close(), but tag the file_type as
const and clean up some minor style issues while moving this.

Add include for fd.h header where needed as well.

Bug 7146.

This streamlines the code a bit and uses more common code.

Parsing logic failed to support underscore in plugin names, which
is now the standard for "cray_aries" configurations.

Improve some descriptions of sdiag output and re-order some
descriptions to match current format.

Bug 7148.

One issue is that batch steps are listed in squeue -s output now.

select/cons_res is recommended.

Bug 7138

Bug 6912.

The sacct command in verison 19.05 when job ID is specified will
find all examples of that job ID run at any time. That means if
the job IDs numbers wrap around, this test will always fail. This
adds a start time to the sacct command of 00:00 (midnight of current
day) to avoid problems with wrapping job IDs and make this test
work more like it did in version 18.08. Note this test does have
a very tiny window for failures if the test program ran just before
midnight and the sacct command to view it's state ran just after
midnight. Given that the entire test only runs for a minute, that
is unlikely in practice.

The fix for bug 7066 will break the original version of this test

bug 7066

Update NEWS, slurm.spec, and slurm.spec-legacy as well.

to match the other log messages that already print signal numbers.

Bug 6938.

This change avoid some operations on a node's GRES data
structure if the count of available GRES is zero.

bug 6997

The NULL size bitmap should be fixed in previous commit,
but this is an added check for improved code stability
in case something else goes wrong.

bug 6997

Previously with a configuration including FastSchedule=1 or 2,
GRES with files defined in gres.conf, and in the node configuration
either specified with a count of 0 or not included at all then
the node's GRES data would be built with a topology array containing
a GRES bitmap of zero size, resulting in an abort when trying to
operate on that bitmap.

bug 6997

Bug 6997

Bug 6987.

Commit: 03165950

Bug 6466.