I just realized that for pushes before https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&searchStr=linux%2Cx64%2Casan%2Cmochitests%2Ctest-linux64-asan%2Fopt-mochitest-devtools-chrome-e10s-4%2Cm%28dt4%29&revision=53c79fdf66930a1ab892051b0edcf404bc1670e6, the test was running in dt5, not in dt4, so we need to take that into account when doing the retriggers.
Bug 1559547 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I just realized that for pushes before [53c79fdf66930a1ab892051b0edcf404bc1670e6](https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&searchStr=linux%2Cx64%2Casan%2Cmochitests%2Ctest-linux64-asan%2Fopt-mochitest-devtools-chrome-e10s-4%2Cm%28dt4%29&revision=53c79fdf66930a1ab892051b0edcf404bc1670e6), the test was running in dt5, not in dt4, so we need to take that into account when doing the retriggers.
I just realized that for pushes on inbound before [53c79fdf66930a1ab892051b0edcf404bc1670e6](https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&searchStr=linux%2Cx64%2Casan%2Cmochitests%2Ctest-linux64-asan%2Fopt-mochitest-devtools-chrome-e10s-4%2Cm%28dt4%29&revision=53c79fdf66930a1ab892051b0edcf404bc1670e6), the test was running in dt5, not in dt4, so we need to take that into account when doing the retriggers. And for autoland, all pushes before [ec36c52abdd5068d6297d10d40e60e00ef82e7f0](https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception%2Crunnable&searchStr=linux%2Cx64%2Casan%2Cmochitests%2Ctest-linux64-asan%2Fopt-mochitest-devtools-chrome-e10s%2Cm%28dt&revision=ec36c52abdd5068d6297d10d40e60e00ef82e7f0) were also running the test in dt5 instead of dt4