Previously if partition limits enforcement was not configured,
  then a job submitted to a partition it could not access (say
  due to AllowGroups, AllowUsers, etc.) would not be rejected,
  but would be allocated resources and run. This bug was
  introduced in commit edf3880c

The initgroups()/getgrouplist() caching in slurmd is changed to not require enumeration, instead individual entries are cached when first needed. This cache is always enabled, thus the CacheGroups configuration setting has been removed. The time that each cache entry is considered valid is determined by the GroupUpdateTime configuration parameter. scontrol reconfig will purge the cache. The default value for the GroupUpdateForce configuration parameter has changed, as systems where /etc/group contains all the groups instead of some external system like NIS, LDAP are nowadays probably the exception rather than the rule.

For slurmctld, the group cache still uses enumeration, but this is needed only to take care of special situations like multiple groups with the same GID. With enumeration disabled, group caching still works otherwise. validate_groups() does a little more optional work in order to handle the case where the user primary group is in the AllowGroups list, but getgrnam_r() does not return that user as a group member.

bug 1629

If a node is out of memory, then the malloc performed by slurmstepd
  periodically may fail, killing the slurmstepd and orphaning it's
  processes.
bug 2341

Backfill scheduling fix: If a job can't be started due to a "group" resource
    limit, rather than reserve resources for it when the next job ends, don't
    reserve any resources for it. The problem with the original logic is that
    if a lot of resources are reserved for such pending jobs, then jobs futher
    down the queue may defered when they really can and should be started. An
    ideal solution would track all of the TRES resources through time as jobs
    start and end, but we don't have that logic in the backfill scheduler and
    don't want that extra overhead in the backfill scheduler.
bugs 2326 and 2282

bug 2303

Conflicts:
	src/api/partition_info.c

Handle unexpectedly large lines for hostlists. (Bug 2333.)

While here rework to avoid extraneous xstrcat calls by using
xstrfmtcat instead of snprintf + xstrcat. Collapse line end into
own string for readability.

No performance or functional change, aside from removing possible
line truncation (which will silence additional Coverity warnings).

Removes a double xfree() in slurm_sprint_reservation_info().

When a reservation is created or updated, compress user provided node names
    using hostlist functions (e.g. translate user input of "Nodes=tux1,tux2"
    into "Nodes=tux[1-2]").
bug 2333

Reported by CLANG
Continuation of 7eff526c

Reported by CLANG
Continuation of 7eff526c

Match behavior of other PBS-like resource managers. Bug 2330.

using TRES as a key word.

statements.

Don't allow user specified reservation names to disrupt the normal
    reservation sequeuece numbering scheme.
bug 2318

Conflicts:
	NEWS

anything.  The slurmd will process things correctly after the fact.

The restriction from Cray has been lifted.
bug 2317

Otherwise upgrading slurm on a compute node while tasks are running
will cause plugin mismatch, as slurmstepd would not load the library
until task completion before. Bug 2319.

Job step constraints applied to active rather than available features
Use active rather than available features for non-stop node replacements

Bug 2228

Bug 2228

The restriction from Cray has been lifted.
bug 2317

Expect sometimes has trouble parsing the output file of this test.
The test has been modified to decrease the output file size, which
seems work better. Note: No change in what is being tested.