Closed
Bug 1352930
Opened 8 years ago
Closed 7 years ago
Intermittent dom/media/tests/mochitest/test_peerConnection_basicAudioPcmaPcmuOnly.html | application timed out after 330 seconds with no output
Categories
(Core :: WebRTC, defect, P4)
Core
WebRTC
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure)
Filed by: bclary [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=88194156&repo=mozilla-central
https://autophone.s3.amazonaws.com/v1/task/LfahRbGpT3KL34GrfaTo8g/runs/0/artifacts/public/build/mochitest-webrtc-mochitests-webrtc-debug.ini-1-nexus-6-1-845376d2-145b-4291-91ed-d3d28e90044c.log
Updated•8 years ago
|
tracking-fennec: --- → ?
Comment 1•8 years ago
|
||
Have you seen other failures with the following in the logging?
"Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
"
backlog: --- → tech-debt
Rank: 35
Flags: needinfo?(bob)
Priority: -- → P3
Updated•8 years ago
|
Comment 2•8 years ago
|
||
This may be fall out due to bug 1352892.
Blocks: 1352892
Flags: needinfo?(bob)
tracking-fennec: ? → +
Comment hidden (Intermittent Failures Robot) |
Comment 4•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•