Open Bug 1271028 Opened 8 years ago Updated 2 years ago

Fix and re-enable browser_state_notifications.js on e10s


(Core :: DOM: Core & HTML, defect)




Tracking Status
e10s + ---
firefox49 --- wontfix


(Reporter: RyanVM, Unassigned)


(Blocks 2 open bugs)


Looks like this test is a bit of a dumpster fire in general. Probably needs a good hard looking at.

19:55:16     INFO -  366 INFO TEST-START | dom/base/test/browser_state_notifications.js
19:55:16     INFO -  Not taking screenshot here: see the one that was previously logged
19:55:16     INFO -  367 INFO checking window state
19:55:16     INFO -  368 INFO TEST-UNEXPECTED-FAIL | dom/base/test/browser_state_notifications.js | Exception thrown - This test didn't call add_task, nor did it define a generatorTest() function, nor did it define a test() function, so we don't know how to run it.
19:55:16     INFO -  MEMORY STAT | vsize 720MB | residentFast 201MB | heapAllocated 76MB
19:55:16     INFO -  369 INFO TEST-OK | dom/base/test/browser_state_notifications.js | took 115ms
Blocks: 987493
Component: DOM → DOM: Core & HTML

NI myself to see if we can re-enable this now.

Flags: needinfo?(ryanvm)

Still permafailing with the same error as before.

Flags: needinfo?(ryanvm)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.