Which in this case is what has happened since the launch failed.

since the slurmd will send the same message.

correctly.

ran inside the allocation can read the environment correctly.

Wait up to 20 seconds for gres.conf file before exiting.

This fixes some problems creating advanced reservations on heterogeneous systems, especially when core counts are specified in the reservation.
bug 1068

Make "srun --gres=none ..." work when executed without a job allocation
(i.e. srun creates the allocation plus the step). Previous logic would
try to create the job with a gres value of "none".

Fix for possible error if job has GRES, but the step explicitly requests a
GRES count of zero.

BlueGene/Q's runjob command requires a fully qualified pathname,
so only for that machine type, resolve the name in srun. This
partitially reverts commit 57efc873
but only for BGQ systems.

and only caused confusion since the cpu_bind options mostly refer to a
step we opted to only allow srun to set them in future versions.

Defer job step initiation of required GRES are in use by other steps rather
than immediately returning an error.
bug 1056

had --network= specified.

ProfileHDF5Dir directory as well as all it's sub-directories and files.

This isn't the case in the current code so this isn't as big of a deal.

This logic will also be removed in 14.11 so it become less of a deal as
well, but just to be safe we cover the base.

be used for AcctGatherFilesystemType.

look at any other day for -D jobs)

srun properly interprets a leading "." in the executable name based upon
the working directory of the compute node rather than the submit host.

script that will use it.

states.

has finished)

Arguments in wrong order