Expect is unable to work with more than 32-bit numbers, so it can't
properly test task affinity on KNL with 272 threads

- 2 x Integer handling issues (CONSTANT_EXPRESSION_RESULT)

Warning flag -Wempty-body in clang-3.7 now errors on this, split
macro definition up over multiple lines to silence.

Fix a memory leak on error conditions and a possibly unterminated string
  as reported by Coverity

Revision to 06fbdd75
  Previous logic was causing tests 1.87 and 15.19 to fail sometimes
  due to a race condition by adding a "Job allocation revoked"
  message to salloc output even if no allocation occured.
bug 3351

this is a corrections to some of the ligic in commit 3851f619
  that commit set a pointer to NULL, which it should not have.

Bug introduced yesterday in commit 239cfa96

Several possibly unterminated string operations
Several memory leak fixes

This is a revision of commit 72d8d9b7,
  which introduced a parsing bug

Fix several memory leaks and possible out-of-bound memory references
  reported by Coverity.

Bad array pointer for srun --no-alloc
Added function error check in srun
Memory leak in sstat

Fix several memory leaks and other high-priority errors reported by Coverity

instead of calling g_slurm_auth_get_uid again.

Add SchedulerParameters option of spec_cores_first to select specialized
    cores from the lowest rather than highest number cores and sockets.
bug 3349

Previous logic was failing if no specialized cores configured on node
  and job wanted to configure some
bug 3349

Null terminate before strchr().

This is a new message when "PrologFlags=contain" or
  "PrologFlags=alloc" is configured.
bug 3351

Cancel interactive job if Prolog failure with "PrologFlags=contain"
    configured.
bug 3351

Minor fix to commit 1e6b7522 in
  the case where user specification of specialized cores is disabled.
bug 3349

If a job specifies --core-spec and the node has identified specialized
  cores using the CpuSpecList option which are not the default cores
  (e.g. the first cores rather than the last cores on each socket),
  the the user's cores will be selected from those identified in the
  configuration.
bug 3349

This requires dealing directly with the running cluster and mucking
with it's database.

(user, account, cluster)