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

Improve scheduling of jobs in reservations that overlaps other reservations.
bug 1051

had --network= specified.

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

be used for AcctGatherFilesystemType.

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.

Fix sbatch --export=ALL, it was treated by srun as a request to explicitly
export only the environment variable named "ALL".
bug 1045

has finished)

timeout when talking to the Database is the same timeout so a race
condition could occur in the requesting client when receiving the response
if the database is unresponsive.

the entire cnode.

Fix SelectTypeParameters=CR_PACK_NODES for srun making both job and step
resource allocation. Previously a stand-long srun command would distribute
tasks evenly across the nodes.

Start a job in the highest priority partition possible, even if it requires
preempting other jobs and delaying initiation, rather than using a lower
priority partition. Previous logic would preempt lower priority jobs, but
then might start the job in a lower priority partition and not use the resources
released by the preempted jobs.
bug 1032

together.

line buffered.

Job array dependency based upon state is now dependent upon the state of
the array as a whole (e.g. afterok requires ALL tasks to complete
sucessfully, afternotok is true if ANY tasks does not complete successfully,
and after requires all tasks to at least be started).

Count is reset running array tasks on reconfig

sched/backfill - Set expected start time of job submitted to multiple
partitions to the earliest start time on any of the partitions.
Previous logic would set the time to that of the last partition
tested.

Previously job would only run in first listed partition.

Fix gang scheduling for jobs submitted to multiple partitions.
Previous logic assumed the job's "partition" field contained a
single partition name, that in which the job is running. That
was recently changed in order to support job's being requeued,
which we want to be runable in all of it's valid partitions.

Added squeue -P/--priority option that can be used to display pending jobs
in the same order as used by the Slurm scheduler even if jobs are submitted
to multiple partitions (job is reported once per usable partition).

instead of guessing off the exit_code.

signal 1.