Previous logic only reported un-reserved node map.
New logging adds information about each job testing and where/when
it is scheduled resources.

slurm.conf when using the DBD.

Induced by bf_continue option and deleting a partition.

to reflect only the latest supported format.

if bf_continue option is configured and slurm is reconfigured during
one of the sleep cycles, then the backfill scheduler will reference
an invalid partition pointer.

Previous logic would place more tasks on each node than specified
by --ntasks-per-node, using fewer nodes than desired. This only
happens with exclusive node allocations (e.g. in partition
configuration Shared=Exclusive).

EpilogSlurmctld pthread is passed required arguments rather than a pointer
to the job record, which under some conditions could be purged and result
in an invalid memory reference.

EpilogSlurmctld pthread is passed required arguments rather than a pointer
to the job record, which under some conditions could be purged and result
in an invalid memory reference.

reboot of a block if only jobs in the list are running on it when cnodes
go into a failure state.

_p_ in the plugin function names
_g_ in the global function names

This functionality has been obsoleted by the LogTimeFormat.

Modify slurmctld message retry logic to support Cray cold-standby SDB.

From "Missing time limit" to
"Time limit specification required, but not provided"

segfault.

is not parsed correctly.

gres/gpu and gres/mic - Do not treat the existence of an empty gres.conf
file as a fatal error. There may be no gres devices on that node so we
do not require the file. Assume gres counts of zero if no file.

bug 436

bug 436

just print the job ID rather than "Submitted batch job #"

job CPU count not loaded correctly
Partition time limit format wrong (minutes rather than hhmmss format).

Convert bitmap functions to use int32_t instead of int in data structures
and function arguments. This is to reliably enable use of bitmaps containing
up to 4 billion elements. Several data structures containing index values
were also changed from data type int to int32_t:
- Struct job_info / slurm_job_info_t: Changed exc_node_inx, node_inx, and
  req_node_inx from type int to type int32_t
- job_step_info_t: Changed node_inx from type int to type int32_t
- Struct partition_info / partition_info_t: Changed node_inx from type int
  to type int32_t
- block_job_info_t: Changed cnode_inx from type int to type int32_t
- block_info_t: Changed ionode_inx and mp_inx from type int to type int32_t
- Struct reserve_info / reserve_info_t: Changed node_inx from type int to
  type int32_t

isn't doing the launching.

updated the srun man page.

sched/backfill - Prevent possible memory corruption due to use of
bf_continue option and long running scheduling cycle (pending jobs could
have been cancelled and purged).

Change max message length from 100MB to 1GB before generating "Insane
message length" error.

can only be a TORUS (1).