Comment 2 for bug 433323

Following the "Spurious test failure" procedure, Gary determined the failure could not be reproduced locally and then disabled the test, landed it, and filed this bug.

Perhaps it doesn't need to be fixed in 3.0 but the test needs to be investigated and re-enabled. Re-target if you think 3.1.10 is more appropriate.