Closed Bug 1438693 Opened 7 years ago Closed 7 years ago

browser_privacypane.js is going to permafail when Gecko 60 merges to Beta on 2018-03-01

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
Firefox 60
Tracking Status
firefox-esr52 --- unaffected
firefox58 --- unaffected
firefox59 --- unaffected
firefox60 + verified

People

(Reporter: aryx, Assigned: osmose)

References

Details

Attachments

(1 file)

https://treeherder.mozilla.org/logviewer.html#?job_id=162522293&repo=try Bug 1426482 which added the file has status-firefox59 set to "affected". If that will be fixed on beta, forward-porting should be easy. At the moment, the tests return if the build isn't a Nightly. [task 2018-02-15T21:21:24.202Z] 21:21:24 INFO - TEST-START | browser/components/preferences/in-content/tests/browser_privacypane.js [task 2018-02-15T21:21:24.223Z] 21:21:24 INFO - TEST-INFO | started process screentopng [task 2018-02-15T21:21:24.669Z] 21:21:24 INFO - TEST-INFO | screentopng: exit 0 [task 2018-02-15T21:21:24.670Z] 21:21:24 INFO - Buffered messages logged at 21:21:24 [task 2018-02-15T21:21:24.670Z] 21:21:24 INFO - Entering test bound testBrowserErrorInitialValue [task 2018-02-15T21:21:24.670Z] 21:21:24 INFO - Leaving test bound testBrowserErrorInitialValue [task 2018-02-15T21:21:24.670Z] 21:21:24 INFO - Entering test bound testBrowserErrorLearnMore [task 2018-02-15T21:21:24.670Z] 21:21:24 INFO - Leaving test bound testBrowserErrorLearnMore [task 2018-02-15T21:21:24.672Z] 21:21:24 INFO - Buffered messages finished [task 2018-02-15T21:21:24.674Z] 21:21:24 INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/in-content/tests/browser_privacypane.js | This test contains no passes, no fails and no todos. Maybe it threw a silent exception? Make sure you use waitForExplicitFinish() if you need it. -
Flags: needinfo?(mkelly)
Assignee: nobody → mkelly
Flags: needinfo?(mkelly)
Hrm, I _think_ I tried that correctly: https://treeherder.mozilla.org/#/jobs?repo=try&revision=bc1afe3d70a131e2022bc470b0b78a695fc95cee&selectedJob=162731903 But it's getting a bunch of build failures. Do I need to include more patches from the linked build? Maybe that inbound merge or something? The patch is pretty simple so I'll probably put it up for review anyway.
Gijs: Any idea if you'll be able to review this soon, given the failures? It should be a very quick review.
Flags: needinfo?(gijskruitbosch+bugs)
(In reply to Michael Kelly [:mkelly,:Osmose] from comment #8) > Gijs: Any idea if you'll be able to review this soon, given the failures? It > should be a very quick review. Uh, I would have reviewed it within 24 hours of it appearing if I'd had any idea it existed. Until you needinfo'd me I was CC'd on neither this nor the blocking bug, and there's no review request on the attachment here (so it doesn't show up in my bugzilla requests page), and this is the entire email I had from Phabricator about this request: ---- phab-bot changed the visibility from "Administrators" to "Public (No Login Required)". phab-bot changed the edit policy from "Administrators" to "All Users". REPOSITORY rMOZILLACENTRAL mozilla-central REVISION DETAIL https://phabricator.services.mozilla.com/D589 EMAIL PREFERENCES https://phabricator.services.mozilla.com/settings/panel/emailpreferences/ To: Osmose, Gijs ---- I did not deduce from that that I needed to review anything. :-\ Are there bugs on file for making phabricator usable for reviewers so this doesn't happen?
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(mkelly)
Comment on attachment 8951757 [details] Bug 1438693: Skip browser_privacypane.js if not a Nightly build. :Gijs has approved the revision. https://phabricator.services.mozilla.com/D599
Attachment #8951757 - Flags: review+
Flags: needinfo?(mkelly) → in-testsuite+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: