# Conflicts:
#	NEWS

and the slurmctld doesn't wait long enough for the response it would give
up leaving the connection open and create a situation where the next message
sent could receive the response of the first one.

Bug 2739

Correct logic that calculates a step's cpus_per_task allocation
on a heterogenous job allocation. Mixing a KNL with a Xeon resulted
in a count that was between the CPU count on the two node types
and invalid on the node with smaller CPU count (e.g. 272 CPUs on
KNL, 8 on Xeon, and 2 tasks, cpus_per_task = 140).

JOB_COMPLETING is a flag and not an enum.

accounting may show job or step in COMPLETING state for a while

Search for step state happened before the step started.

Correction to environment variable name in
commit a09a0795

The default gres=craynetwork:1 prevented more than one step from
  running at a time. Explicitly set gres=craynetwork:0 for jobs
  and steps to avoid this limitation.

- 2 x Integer handling issues (CONSTANT_EXPRESSION_RESULT)

Bug #2713.

Bug #2713.

Remove some SQUEUE output format environment variables set by
  default on Cray systems, which break some tests

AND should have been an OR.
Modify test to log more details on failure.

Group id was being overwritten by user id.

Writing and reading to a file on a slow shared filesytem could cause
this test to fail.

The filesystem may have problems removing and creating the same filename
quickly.

Correct description of the SLURMD_NODENAME environment variable
in the sbatch and srun man pages.

Also add some job time limits

Increase a sleep for slower step start times on a Cray
Make error message more detailed (add expected/actual count to message)

One memory leak fixed
Some other code moved around for better clarity

Run autogen.sh to pickup changes and resolve conflicts.

Previous logic could truncate CPU masks at 32-bits