Comment 4 for bug 1063856

We've retried this test run and it seems to have been a transient event. That being the case it may have been introduced at any point so we can't really invest the time in finding out exactly when. I would say we should close this bug.