Open
Bug 1271028
Opened 9 years ago
Updated 2 years ago
Fix and re-enable browser_state_notifications.js on e10s
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: RyanVM, Unassigned)
References
(Blocks 1 open bug)
Details
Looks like this test is a bit of a dumpster fire in general. Probably needs a good hard looking at.
https://treeherder.mozilla.org/logviewer.html#?job_id=20501539&repo=try#L3972
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
Updated•9 years ago
|
tracking-e10s:
--- → +
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Reporter | ||
Comment 1•3 years ago
|
||
NI myself to see if we can re-enable this now.
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 2•3 years ago
|
||
Still permafailing with the same error as before.
Flags: needinfo?(ryanvm)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•