chutney intervals are too short for successful bootstrap, particularly under high CPU load on OS X
Split from #13718 (moved):
Occasionally, the CPU load on my test machine will increase (or some other condition affecting the scheduler will occur), and a bootstrap race condition will cause the test to fail 50-100% of the time for a few hours. Then it will start working again. The commands run are exactly the same each time. I'll be excluding these results from the tests, because they happen with or without the changes.
Perhaps lengthening some of the default intervals chutney uses would solve this.