Closed Bug 1317864 Opened 9 years ago Closed 7 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | dom/media/tests/mochitest/test_peerConnection_callbacks.html | application timed out after 330 seconds with no output

Categories

(Core :: WebRTC, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: bulk-close-intermittents, intermittent-failure)

Rank: 15
Priority: -- → P1
P1 due to apparent unlock-on-wrong-thread (or unlock a not-locked lock) Assertion failure: lock->locked && pthread_equal(lock->owner, pthread_self())
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Lowering priority because the test appears to fail rarely for different reasons, but the original locking issue any more. > For more details, see: > https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1317864&startday=2017-08-07&endday=2017-08-13&tree=all Assertion failure: aVsyncTimestamp <= TimeStamp::Now(), at z:/build/build/src/layout/base/nsRefreshDriver.cpp:670 > For more details, see: > https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1317864&startday=2017-11-27&endday=2017-12-03&tree=all [task 2017-12-03T00:53:50.689Z] 00:53:50 INFO - GECKO(3044) | # Fatal error in /builds/worker/workspace/build/src/media/webrtc/trunk/webrtc/modules/video_coding/video_codec_initializer.cc, line 181 [task 2017-12-03T00:53:50.689Z] 00:53:50 INFO - GECKO(3044) | # last system error: 0 [task 2017-12-03T00:53:50.692Z] 00:53:50 INFO - GECKO(3044) | # Check failed: streams[i].width > 0 (0 vs. 0) Maybe this test is racy in some way? For now I would say we should keep an eye open for more failures.
Rank: 15 → 25
Priority: P1 → P3
Summary: Intermittent TEST-UNEXPECTED-TIMEOUT | dom/media/tests/mochitest/test_peerConnection_callbacks.html | application timed out after 330 seconds with no output after Assertion failure: lock->locked && pthread_equal(lock->owner, pthread_self()) → Intermittent TEST-UNEXPECTED-TIMEOUT | dom/media/tests/mochitest/test_peerConnection_callbacks.html | application timed out after 330 seconds with no output
We seem to either be waiting forever for the onaddstream callback (maybe it is firing before we set up the listener?), or are waiting forever for the currentTime to advance (I see other intermittents with this exact problem).
Status: REOPENED → RESOLVED
Closed: 8 years ago7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.