Likely regressed by 1547939 which added a bunch of test data that this test will have to churn through, as noted in bug 1521253 comment 10. This is similar to that bug (bug 1521253), though a different timeout limit was exceeded (here, we're exceeding the limit for the whole test bucket, I think?) Though the test bucket here isn't really a "real" test bucket -- this was a "test-verify" run which tries to run the test N times (I don't know what the value of N is), and since this is a particularly-long-running test, apparently N times the test duration is longer than our limit. We probably won't see this happening in practice on TreeHerder, except when this test gets modified (and run through test-verify).
Bug 1548765 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Likely regressed by bug 1547939 which added a bunch of test data that this test will have to churn through, as noted in bug 1521253 comment 10. This is similar to that bug (bug 1521253), though a different timeout limit was exceeded (here, we're exceeding the limit for the whole test bucket, I think?) Though the test bucket here isn't really a "real" test bucket -- this was a "test-verify" run which tries to run the test N times (I don't know what the value of N is), and since this is a particularly-long-running test, apparently N times the test duration is longer than our limit. We probably won't see this happening in practice on TreeHerder, except when this test gets modified (and run through test-verify).