Closed Bug 994351 Opened 11 years ago Closed 11 years ago

media-element-source-seek-1 fails randomly on B2G emulator opt

Categories

(Core :: Audio/Video, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla32

People

(Reporter: jesup, Unassigned)

References

Details

Attachments

(2 files)

This fails with timeouts with the patches for bug 818822 applied; we're going to disable this test for now. We should fix this test or find the underlying bug. We made the test more stable by adding preload="auto" and loop = true; that still left it failing 5-10% of the time (including on local runs of crashtest-remote content/media/test/crashtests) I'll attach a patch used to debug the problem. I'll note that the emulator stops working randomly after some number of runs (I got a max of 70 runs), after which you may need to logout, reboot or even pull and build a new repo (I haven't debugged all the issues here).
Perhaps the cycle was growing the number of events exponentially somehow.
(In reply to Karl Tomlinson (:karlt) from comment #1) > Created attachment 8404332 [details] [diff] [review] > break playing/seeked cycle in test > > Perhaps the cycle was growing the number of events exponentially somehow. Wouldn't the debugs have shown that then?
Comment on attachment 8404285 [details] debugs from the failed runs (locally) (In reply to Randell Jesup [:jesup] from comment #2) > > Perhaps the cycle was growing the number of events exponentially somehow. > > Wouldn't the debugs have shown that then? I guess so. >REFTEST TEST-START | http://192.168.1.17:8888/tests/content/media/test/crashtests/media-element-source-seek-1.html >REFTEST TEST-LOAD | http://192.168.1.17:8888/tests/content/media/test/crashtests/media-element-source-seek-1.html | 68 / 72 (94%) >starting test >connected source to audioElement >onloadedmetadata fired >onloadeddata fired >onplay fired >onplaying fired >onsuspend fired >onwaiting fired >onseeked fired >onplaying fired >onwaiting fired >onplaying fired >onseeked fired >######################## BrowserElementChildPreload.js loaded >TEST-UNEXPECTED-FAIL | http://192.168.1.17:8888/tests/content/media/test/crashtests/media-element-source-seek-1.html | application timed out after 330 seconds with no output This log shows a small number of onplaying/onseeked repeats, but the test would have removed reftest-wait in onseeked, so I guess something is busy, blocking the test harness from continuing. >REFTEST TEST-START | http://192.168.1.17:8888/tests/content/media/test/crashtests/media-element-source-seek-1.html >REFTEST TEST-LOAD | http://192.168.1.17:8888/tests/content/media/test/crashtests/media-element-source-seek-1.html | 68 / 72 (94%) >starting test >connected source to audioElement >onloadedmetadata fired >onloadeddata fired >onplay fired >onplaying fired >onsuspend fired >TEST-UNEXPECTED-FAIL | http://192.168.1.17:8888/tests/content/media/test/crashtests/media-element-source-seek-1.html | application timed out after 330 seconds with no output This is quite different. I tested that a seek on an element that is not playing still generated an onseeked event, so I don't know why the test stopped here. I'll apply attachment 8404332 [details] [diff] [review] to the test, but it may not be the cause of the timeout.
Blocks: 996487
Blocks: 818822
Depends on: 997152
Flags: in-testsuite+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: