Closed
Bug 1304580
Opened 8 years ago
Closed 8 years ago
Intermittent TEST-UNEXPECTED-TIMEOUT | dom/media/tests/mochitest/test_peerConnection_basicAudioDynamicPtMissingRtpmap.html | application timed out after 330 seconds with no output
Categories
(Core :: WebRTC, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1304519
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Filed by: philringnalda [at] gmail.com https://treeherder.mozilla.org/logviewer.html#?job_id=3826997&repo=autoland https://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-win32/1474488360/autoland_win7_ix_test-mochitest-media-e10s-bm109-tests1-windows-build526.txt.gz
Updated•8 years ago
|
Rank: 25
OS: Unspecified → Windows 7
Priority: -- → P2
Hardware: Unspecified → x86_64
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 3•8 years ago
|
||
Chutten, with the logs at [1] and [2] (from brasstacks), is this also bug 1304519? They contain stuff like > [task 2016-09-29T23:04:26.309633Z] 23:04:26 INFO - ###!!! [Child][MessageChannel] Error: (msgtype=0x4C011C,name=PContent::Msg_AccumulateChildHistogram) Closed channel: cannot send/recv > [task 2016-09-29T23:04:26.310868Z] 23:04:26 INFO - [Child 6948] WARNING: MsgDropped in ContentChild: file /home/worker/workspace/build/src/dom/ipc/ContentChild.cpp, line 2295 > [task 2016-09-29T23:04:26.311005Z] 23:04:26 INFO - [Child 6948] WARNING: '!contentChild->SendAccumulateChildHistogram(accumulationsToSend)', file /home/worker/workspace/build/src/toolkit/components/telemetry/TelemetryHistogram.cpp, line 2604 [1] https://public-artifacts.taskcluster.net/Pk8glBdWTcm_Zs1QGC106Q/0/public/logs/live_backing.log [2] https://public-artifacts.taskcluster.net/cQ8trJ22TkmsKpwBF85BoQ/0/public/logs/live_backing.log
Flags: needinfo?(chutten)
Comment 4•8 years ago
|
||
Yup, certainly seems that way. Sorry about that.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(chutten)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•