Introduced in 360fb080. I don't believe this would solve the
underlying issue on a system that is OOM, and there is another
xmalloc call coming up immediately anyways that would then fatal().

# Conflicts:
#	contribs/lua/proctrack.lua
#	src/common/gres.c
#	testsuite/expect/README
#	testsuite/expect/globals

bug6301

Bug 6279

Bug 6214

explicity typecast some size_t variables to long int to avoid
compiler warnings

Bug 5742

Bug 5742

Bug 5742

The information will be logged for all tasks of a job array with
a task count limit.
bug 5093

Bug 6398

On a heterogeneous system the gres.conf coming from various nodes
might not be complete.  The slurm.conf has a complete list of possible
gres on the other hand.

If the GRES doesn't exist we will print an error and use the id instead
of the name, but this should never happen.

Bug 6366

When trying to update the partition list of a job it didn't
get updated.

Bug 6329

bug 5693, 6397

bugs 5693, 6397

put entire description in one line of README file (for logging
add missing exp_continue
remove unused variable

Fix for tests that will fail with SelectTypeParmaters=CR_Socket
(assuming each socket has more than one core).

We want to avoid printing "FAILURE" in the function wait_for_job
as a new use case may result in a job not starting in a timely
fashion and NOT be an error. So change "FAILURE" in wait_for_job
to "WARNING" and add checks for function errors in the tests
as needed (most places already check and log errors).
There were also many cases where "FAILURE would be printed by
wait_for_job, but the job would not have a non-zero exit code
and those are now fixed.

Make sure that the count of CPUs allocated to a job is appropriate
for the task count.
bug 6274

pam_slurm_adopt so special users can ssh to a node. This is an
alternative to pam_access.so.

Bug 6243

Remove unneeded scontrol call.

Bug 6357

Bug 6357

Bug 6357

Bug 6320

instead of first as previously done.

Bug 6004

specific tasks.

Bug 6357

Bug 6004

As noted by Josko Plazonic in the bug report, the tres_usage_in_max
value is bytes, whereas the script expects kb.

Bug 6004

Update seff to reflect API change from rss_max to tres_usage_in_max. Use
Slurmdb::find_tres_count_in_string to parse out the TRES_MEM value.

Bug 6004

This fix is needed to address the GRES specification in gres.conf
having a Type option, while the GRES specification in slurm.conf
does not.

If scontrol is used to change a node's GRES and the input string
contains socket binding information (e.g. "gres=gpu:4(S:0),...")
then ignore the socket binding information input. Use the binding
as reported by slurmd in the node registration.

If a node's GRES has a count of zero (say after updating GRES counts)
then do not print the count. Just don't report anything for that
GRES type.