The previous logic could let a job requiring a persistent burst
buffer start and fail without checking that the buffer already
exists. Was causing regression tests 35.1 and 35.4 to fail.

it would require many changes to the slurm.conf files used in testing
and the functionality being tested here should work the same on
non-cray systems anyway (if it works on a non-cray, the funcitonality
would be fine on a real cray system too).

it would require many changes to the slurm.conf files used in testing
and the functionality being tested here should work the same on
non-cray systems anyway (if it works on a non-cray, the funcitonality
would be fine on a real cray system too).

Change test from select/cray (also used for testing on non-cray
systems) to switch/cray (only used on real cray systems)

This make the test work properly if the default partition configuration
includes a configuration of "OverSubscribe=Exclusive"

Some conditions were resulting in an srun error about no SGI job
container

This fixes a potential task layout problem. Specifically if
a cluster allocates by core and each core contains 2 CPUs and
a job requests 3 tasks and one core on each of two nodes is
available and the first node has one GPU available and the
job requests --gpus-per-task=1 then without this patch
cons_tres would try to put 2 tasks on the first node (one
per CPU). This adds a check of the GPU count in order to
prevent that. Observed sportatically when running regression
tests39.[10-15] in immediate succession on a Cray system
or a system configured with Epilog that takes a few seconds
to complete.

Updated ControlAddr to point to 127.0.0.1 rather than 123.4.5.6

Bug 6794

Bug 6768.

Bug 6779.

Bug 6718.

Replace duplicated text with links, so text that should be the same
does not get out of sync.
Merge out-of-sync text together to get the best of both.
Fix error where line starting with 'nvml' was being omitted.
Minor grammatical and wording fixes.
Improve spacing of paragraphs.
Escape some missed `-` characters.
Remove some statements that are no longer true.
Sundry other minor changes.

An update in gres.conf.5 was not propagated to gres.shtml. Remove the
possibility of that happening again by simply referring the user to
the original doc via a link for more info.

Bug 4717

Bug 6501.

Bug 6791.

Change name of variable for better clarity.
No change in logic

comment and formatting changes

sporadically seeing this problem. Still trying to track down origin.

Correct bad format in log message

Update to commit 02ad8fdd so that locks/unlocks match
if gres.conf not found

gres needs to locally keep the mps_table size rather than use
node_record_count, which gets reset to zero at shutdown.

Check for out of range node index. Not observed, but prevents possible
invalid memory reference.

Copied array without including the array size pointer, so it did
not get freed.