Closed Bug 1391349 Opened 7 years ago Closed 3 years ago

perma failing dom/browser-element/mochitest/test_browserElement_oop_ExposableURI.html in non-e10s mode

Categories

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

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

References

Details

I am turning on non-e10s tests for windows7-debug and noticed a few perma failing tests.

I found dom/browser-element/mochitest/test_browserElement_oop_ExposableURI.html failing:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=01724ecb482db9bad166e86cf46ce32edbccb483&filter-searchStr=mochitest-1

and the log file:
https://public-artifacts.taskcluster.net/QiXt6ZDnTTitDKdyXRJj7Q/0/public/logs/live_backing.log

and related error:
21:42:20     INFO -  2350 INFO TEST-PASS | dom/browser-element/mochitest/test_browserElement_oop_ExposableURI.html | Scheme in string shouldn't be wyciwyg
21:42:20     INFO -  Buffered messages finished
21:42:20  WARNING -  TEST-UNEXPECTED-TIMEOUT | dom/browser-element/mochitest/test_browserElement_oop_ExposableURI.html | application timed out after 330 seconds with no output


I am going to disable this for now so we can get coverage sooner than later.
Blocks: 1391350
Kan-Ru, should we just delete this test?
Flags: needinfo?(kchen)
Priority: -- → P3
Component: DOM → DOM: Core & HTML

test doesn't exist anymore

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(kanru)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.