If running burst_buffer/cray plugin on emulated Cray (NOT a real
   Cray system with Cray APIs) and the burst buffer state information
   includes information about buffers associated with jobs which
   are either completed or no longer exist (i.e. the burst buffer
   state information is old), then ignore that old state information.
   This might possibly be related to bug 3295 if their configuration
   is bad.

Commented out in commit 1e593ebc.

Commented out by commit 86beed44.

Move two functions to static within print.c and slightly
alter types to avoid casts with list_for_each calls.

Also fixes leak of a ListIterator in print_steps_array().

Remove log_oom calls - xmalloc/xrealloc already do this
for us and call abort(), so this is dead code.

Fix a few function declaration formats while here.

Covert bitstring.c to use it instead of BITSTR_SINGLE_FMT and
BITSTRING_RANGE_FMT and remove those.

Use within task/affinity as well so that builds with
USE_64BIT_BITSTR enabled will pass.

Missed the extra comma this introduces; looking at alternate approaches.

This reverts commit 58cd45ae.

Use within dist_tasks.c when printing a bitoff_t to fix compile with
USE_64BIT_BITSTR enabled.

Would only print for affinity before. Change parse method
to strstr() to no longer rely on specific position of plugin
name in the config option.

Bug 3294.

level.

Provide limited support for the MemSpecLimit configuration parameter without
    the task/cgroup plugin.

Revise commit e6ef1f0c
The root cause of the failure is a bug in HWLOC that has since
been fixed in HWLOC version 1.11.5.

If the second call to getgrouplist() found additional groups,
ngroups will be overwritten with this new larger value, while
the gids list would be truncated. (ngroups is a value-result arg.)
This will then lead to _gids_cache_lookup() returning the wrong
number of groups including invalid parts of memory, which are likely
to include some zeros.

Those zeros could then make it to the setgroups() call and thus
give the user access to the root group. Especially as setgroups
will succeed as long as the array does not contain -1 as a gid.

Bug 3320.

task/cgroup - Change error message if CPU binding can not take place to
    better identify the root cause of the problem. Specifically, if
    the hwloc_get_obj_below_by_type() function call completely fails
    that is likely due to task/affinity not being configured, so
    cpusets are not configured. Previous message was
    "task/cgroup: task[%u] infinite loop broken while trying to provision compute elements using %s (bitmap:%s)"
    The new message is
    "task/cgroup: hwloc_get_obj_below_by_type() failing, task/affinity plugin also required"

uint32_t needs %u on 32-bit platforms. Noticed by clang/travisci.

Test would fail if more than one task per core and SelectTypeParamers
  included CR_ONE_TASK_PER_CORE

Bug 3258

This reverts commit 55cb7973.

This reverts commit 817c2ca4.

# Conflicts:
#	NEWS

The test is still failing for me (along with a bunch of others),
  but this change at least gets the test started.