This seems to have been fixed by Two Try runs with a test-verify run for this test:, based off of two consecutive changesets: - based off of https://hg.mozilla.org/try/rev/1ad359b23bed0f2c176553ac7dc2e5f7603f1a08 (older): https://treeherder.mozilla.org/jobs?repo=try&revision=958470f54355389fe03783ae4975baaf667a8c19 Result: Orange with `TEST-UNEXPECTED-TIMEOUT` - based off of https://hg.mozilla.org/integration/autoland/rev/30598180cf6b21d1492ebdad809c3b734eb80850 (newer): https://treeherder.mozilla.org/jobs?repo=try&revision=f121909f8d61b11fa91e418d30b04fe2817c6937 Result: green / test passed So this was fixed by 30598180cf6b21d1492ebdad809c3b734eb80850 (a backout of the initial landing of bug 1887063 for other test failures). This was just another manifestation of some issues in the initial landing of that patch. But in any case, this isn't an issue with up-to-date mozilla-central, where bug 1887063 has long since been re-landed with the issues addressed. --> Resolving as FIXED, and adding dependency on bug 1887063 to tie them together (since this was sort-of a followup for that bug, albeit one that was resolved immediately, it turns out).
Bug 1888279 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This seems to have been fixed by Two Try runs with a test-verify run for this test:, based off of two consecutive changesets: - based off of https://hg.mozilla.org/try/rev/1ad359b23bed0f2c176553ac7dc2e5f7603f1a08 (older): https://treeherder.mozilla.org/jobs?repo=try&revision=958470f54355389fe03783ae4975baaf667a8c19 Result: Orange with `TEST-UNEXPECTED-TIMEOUT` - based off of https://hg.mozilla.org/integration/autoland/rev/30598180cf6b21d1492ebdad809c3b734eb80850 (newer): https://treeherder.mozilla.org/jobs?repo=try&revision=f121909f8d61b11fa91e418d30b04fe2817c6937 Result: green / test passed So this was fixed by 30598180cf6b21d1492ebdad809c3b734eb80850 (a backout of the initial landing of bug 1887063, with the backout-reason being some other test failures). This was just another manifestation of some issues in the initially-landed version of that patch. But in any case, this isn't an issue with up-to-date mozilla-central, where bug 1887063 has long since been re-landed with the issues addressed. --> Resolving as FIXED, and adding dependency on bug 1887063 to tie them together (since this was sort-of a followup for that bug, albeit one that was resolved immediately, it turns out).