Closed Bug 1254352 Opened 5 years ago Closed 5 years ago
_ext _bookmarks .html is permafailing on aurora after the 47 uplift
This test has been permafailing ever since 47 moved to aurora this morning: https://treeherder.mozilla.org/logviewer.html#?job_id=2097357&repo=mozilla-aurora We suspect one of the things bsilverberg landed in the last day or two prior to uplift (likely bug 1252250). Bob, can you look into this and either backout or fix whatever's wrong on aurora (and likely fix it on trunk so we don't have this again on the next uplift cycle)? This will likely block being able to reopen aurora until it's fixed.
5 years ago
Severity: normal → major
5 years ago
Version: unspecified → 47 Branch
:( This looks like bug 1253827 again. Somehow the merge botched version of this patch made it to Aurora.
From #developers: 4:52 PM <John-Galt> KWierso: Hm. Re bug 1254352, the broken version of that test is in the last commit of the failing build, but isn't in the last commit that you pushed... 4:53 PM <John-Galt> https://hg.mozilla.org/releases/mozilla-aurora/file/a06ac8e3220a/toolkit/components/extensions/test/mochitest/test_ext_bookmarks.html vs. https://hg.mozilla.org/releases/mozilla-aurora/file/9a446438d3a4/toolkit/components/extensions/test/mochitest/test_ext_bookmarks.html
Sorry, but I'm not sure what needs to be done to fix this. Do we need to uplift the fixed merge that Kris pushed, or can we just back this out on Aurora?
I guess keep an eye on https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora&fromchange=8849dd1a4a79&group_state=expanded&filter-searchStr=mochitest%20(5)&tochange=9a446438d3a4 to see if the tests on the top push all come back green. I'm not sure why some of them are passing and some aren't.
We did two sets of builds on the merge to aurora - one set on the actual tip cset of the merge, 8849dd1a4a79, and one on a06ac8e3220a which is the tip of the fake separate push that results from bug 1174273. Unsurprisingly, those didn't go particularly well.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.