a nice little segfault.

This picked up recent changes in configure.ac

Run pre_run after persistent buffer creation per Cray documenation

Add logic to burst_buffer/cray and generic to set job's buffer size
  in TRES array for limits and accounting. This includes only the
  the job-specific buffers, not persistent buffers, which will be
  handled separately.

The problem is that with high rate profiling, the cpu usage becomes a
binary field (see the output below). I would like to have a more accurate
value of the cpu usage. I'm thinking about writing another profiling
plugin that may be very useful in our environment, and probably also in
other environments where compute nodes are shared.

Bug 1748

change is to ease future transition to IPv6 reducing the number of
places that use AF_INET.  AF_SLURM currently points to AF_INET though.

char in the tres string.

removed, so make sure we process correctly, sort it while we are at it.

slurmdb_combine_tres_strings.

Bug 858

Plus some cosmetic changes to a couple of tests

end up pointing to qos_ptr_2 erroneously.

clearing the pointer in the partition record.

Fix case where job would get the wrong cpu count when using --ntasks-per-core and --cpus-per-task together.

Bug 1370