Comment 7 for bug 1455627

Well, I've discovered there's a race condition somewhere around suite initialization, which is causing the test to fail intermittently, and not due to heavy machine load (i.e. my fix for calculating the timeout according to time it takes on the actual machine running it *was* correct, but it uncovered the race).