this is related to commit 845e134b
when a step ends, flag that it is done on ALL nodes so that it's
memory can be released. Note that test1.19 would fail in front-end
mode when there was a default memory allocation. That test would
spawn 2 steps, but the first would not release its memory when
that step ended, so the second step would not start.

this is useful for testing. it is unclear why this was disabled

Bugs 5699, 5700, 5701

Bug 5698

Bug 5701

Bug 5701

Bug 5700

Bug 5700

Bug 5699

Bug 5699

Bug 5699

Bug 5699

Bug 5699

Bug 5699

Bug 5699

It doesn't do anything yet.

Two tests were failing when using --enable-front-end configuration

# Conflicts:
#	NEWS
#	src/common/hostlist.c

hosts in each list.

Bug 5741

by integers.

We understand this reverts bc7b91cd, but in all our testing we have
been unsuccessful finding what that commit actually does.

Bug 5711
Bug 5746

This fixes a problem if a job has a gres_per_job value set and
multiple required nodes (by name). Previous logic could block
use of later nodes if the gres_per_job value was reached by
earlier selected nodes.

This reverts commit 204da0b6.

# Conflicts:
#	NEWS

So this takes us back to 204da0b6.

See bug 5746

distribution.

Bug 5706

Previous logic would fail to skip over comma when gres name is
followed immediately by a comma and no count
Also remove logic to set pointers that were not used later

bug 5743

with some configurations and given a race condition test39.7 would
fail. This corrects some bad logic (failing to update CPU count when
cores are removed from consideration)

bug 5745

In some cases test1.88 failed due to specifying a node count range,
"-N 1-6".

Used "<" instead if "<<"

changes only apply to non-standard task distribution options:
serial, lln, spread, and busy