This will fix a similar problem to #8928, which seems to correlate with CPU load on the host system running the test suite.