Note that the reason why the retriggers point to 1637463 is because this test modified the way the tests are chunked. So the dt1 job before this push didn't contain the same tests. Now, either the new chunks are making the failure permanent because of a side effect between two suites. Or it only confused the retriggers, and we would find the failure on another dt* job.
Bug 1641824 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Note that the reason why the retriggers point to 1637463 is because this patch modified the way the tests are chunked. So the dt1 job before this push didn't contain the same tests. Now, either the new chunks are making the failure permanent because of a side effect between two suites. Or it only confused the retriggers, and we would find the failure on another dt* job.
Note that the reason why the retriggers point to 1637463 is because this patch modified the way the tests are chunked. So the dt1 job before this push didn't contain the same tests. Now, either the new chunks are making the failure permanent because of a side effect between two suites. Or it only confused the retriggers, and we would find the failure on another dt* job. Edit: According to https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedTaskRun=SR_cztUlQNi-kiLDHAUWfA.0&searchStr=linux%2C18.04%2Cx64%2Cdebug%2Cmochitests%2Cwith%2Cfission%2Cenabled%2C&revision=2a44daf61d7f452aaf55f47c2962f8c2ed625704 , the failure was previously in dt4