Open Bug 1592777 Opened 5 months ago Updated 12 days ago

Fix browser/base/content/test/popupNotifications/browser_popupNotification_3.js for fission

Categories

(Toolkit :: Notifications and Alerts, task, P2)

task

Tracking

()

Fission Milestone M4.1

People

(Reporter: ddurst, Unassigned, Mentored, NeedInfo)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Currently browser/base/content/test/popupNotifications/browser_popupNotification_3.js is skipped for opt and debug.

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?
Fission Milestone: ? → M4.1

Ethan says this test is blocked waiting for RemoteWebProgress onLocationChange bug 1580752.

Depends on: 1580752

Matt, this bug is a blocker for Fission's M.1 milestone (aka "fix all the mochitests"), but it's currently unassigned. The Fission team is hoping teams will fix their mochitests for Fission before the end of Q1 (75 or 76 Nightly).

Is this bug blocked waiting for RemoteWebProgress onLocationChange bug 1580752 (as I reported in comment 2 that Ethan Tseng said)? kmag said (in bug 1580752 comment 4) that he doesn't think bug 1580752 is blocking anything.

Will your team be able to prioritize this bug for Q1? If you don't think this mochitest failure should block shipping Fission, just let me know.

Flags: needinfo?(MattN+bmo)

I haven't had time to look into this test.

You need to log in before you can comment on or make changes to this bug.