Increase odds that a running job stays running during a test
Increase odds that a running job stays running during a test

We've seen sporadic failures in CI with jobs like this, where we test
quorum thresholds by keeping one node busy while the test job runs.  I
suspect that on some test boxes, depending on load, this busy job
actually finishes before the test job starts, making the node
available, and screwing up our test.

chef/oc-pushy-pedant,chef/oc-pushy-pedant,chef/oc-pushy-pedant