If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Fix and re-enable browser_state_notifications.js on e10s

NEW
Unassigned

Status

()

Core
DOM
a year ago
a year ago

People

(Reporter: RyanVM, Unassigned)

Tracking

(Blocks: 2 bugs)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s+, firefox49 affected)

Details

(Reporter)

Description

a year ago
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
(Reporter)

Updated

a year ago
Blocks: 987493
tracking-e10s: --- → +
You need to log in before you can comment on or make changes to this bug.