Phil and I independently found a chunk of duplicate code that can be eliminated with no change to the functionality.  This is against the 2.4 branch.
Don

Conflicts:
	src/slurmctld/reservation.c

isn't up at the time the slurmctld starts, not running the
priority/multifactor plugin, and then the database is started up later.

This is a backport of plugin initialization logic made in the
select/serial branch that we want to have in SLURM v2.4 and not
only in v2.5. Note the plugin logic in v2.5 is different and
this changes to not apply

Previous code could result in invalid memory reference.

Avoiding a slurmctld crash when scheduling problems due to resources. Setting an ADMIN hold instead.

Cray - Improve support for zero compute note resource allocations.
Partition used can now be configured with no nodes nodes.

Conflicts:
	NEWS

Conflicts:
	META

The symptom is that SLURM schedules lower priority jobs to run when higher priority, dependent jobs have their dependencies satisfied.  This happens because dependent jobs still have a priority of 1 when the job queue is sorted in the schedule() function.  The proposed fix forces jobs to have their priority updated when their dependencies are satisfied.

and task count that isn't an even cut.