First noticied by Brian.

It was leaking memory otherwise

Not used here.

Commit 63b7e3a8 changed the --mem limit to 1MB for the job if
not using a memory SelectType, but this can cause the job to fail
if the JobAcctGatherFrequency is frequent enough to notice that the
"sleep" command is using more than 1MB of resources.

Refactor test to avoid specifying job memory. Use --wrap to avoid
creating a temporary job script as well.

Commit 63b7e3a8 changed the --mem limit to 1MB for the step if
not using a memory SelectType, but this can cause the job to fail
if the JobAcctGatherFrequency is frequent enough to notice that the
"sleep" command is using more than 1MB of resources.

Refactor test to avoid specifying job memory. Use --wrap to avoid
creating a temporary job script.

Commit 63b7e3a8 changed the --mem limit to 1MB for the step if
not using a memory SelectType, but this can cause the job to fail
if the JobAcctGatherFrequency is frequent enough to notice that the
"sleep" command is using more than 1MB of resources.

Refactor test to avoid specifying memory memory; and since only one
step is checked for, only run a single step in the job. Use --wrap
to avoid creating a temporary job script.

This bug was introduced in commit 93adc329
Symptom is failure of test 2.7

Some portions of tests 21.30 and 21.34 failed with accounting and
priority basic. These changes disable portions of those tests as
needed based upon configuration.

FreeBSD requires this to build; overlooked in 2d9e999f.

Update information about modified functions and data structures.

It was leaking memory otherwise

_allocate_sc() is heavily used within the scheduler, change to
stack allocation from heap to avoid constant churn on xmalloc()/xfree().

Bug 3420.

"can be taken out 2 versions past 15.08"... we're now three past.

Unlink from build, remove and remove fallback call to it in sh5util.c.

test1.63 was failing periodically due to a race condition. A signal
  was being sent to srun before the signal handler thread was spawned.