Closed Bug 1239237 Opened 8 years ago Closed 2 years ago

Intermittent e10s test_websocket.html | application timed out after 330 seconds with no output

Categories

(Core :: DOM: Workers, defect, P5)

Product:
Core
Component:
DOM: Workers
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: philor, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure)

Blocks: e10s-tests
tracking-e10s: --- → +
On OSX, this appears to often be accompanied by:
Assertion failure: answer == true || mEventQueue.IsEmpty() (Should always enqueue if ChannelEventQueue not empty), at /builds/slave/try-m64-d-00000000000000000000/build/src/obj-firefox/dist/include/mozilla/net/ChannelEventQueue.h:108
See Also: → 1237807
Intermittent e10s test failure
Priority: -- → P5

Bulk closing some old intermittents.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.