Closed Bug 1345741 Opened 7 years ago Closed 3 years ago

dom/media/test/test_playback.html | application timed out after 330 seconds with no output

Categories

(Firefox for Android Graveyard :: Audio/Video, defect, P5)

ARM
Android
defect

Tracking

(fennec+)

RESOLVED INCOMPLETE
Tracking Status
fennec + ---

People

(Reporter: bc, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(6 files)

dom/media/test/test_playback.html is part of both the Autophone Mdm and Mm test manifests.

I have disabled the tests which cause the test jobs to have failures.

An example try run with the tests disabled is green:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=8137ac67c95659858fa4e54d58b321c9fd68b3a3&filter-searchStr=Mm

An example try run with the tests enabled along with a slight change to isSlowPlatform to make all Android versions slow platforms is orange except on Android 4.2:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=e518d39ff8b003ab21bf0d7270fa6e3547c0a7a8&filter-searchStr=Mm

with individual failures like:

22 INFO TEST-UNEXPECTED-FAIL | dom/media/test/test_playback.html | resolution-change.webm-42 timed out!

INFO TEST-UNEXPECTED-FAIL | dom/media/test/test_playback.html | bipbop-lateaudio.mp4-57 timed out!

etc.

Increasing the per test time out for slow platforms causes fennec to hang without output for 330 seconds

https://treeherder.mozilla.org/#/jobs?repo=try&revision=f44dc1db928772642e05a35461b2259c1505df91&filter-searchStr=Mm

Adding a SimpleTest.requestLongerTimeout(3) does not affect the no output hang:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=b5f1854b85c6abbf9941a1ad934ae0c33d1e2e77&filter-searchStr=Mm
patch to prevent the test run from terminating if 4 timeouts occur.
patch to make all android versions slow platforms.
patch to remove all of the skip-if in the autophone-media.ini manifest.
patch to increase the per test timeout for slow platforms.
patch to request complete logs on slow platforms.
patch to increase the timeout by a factor of 3 on slow platforms.
try commit message to run Mm on autophone:

try: -b do -p android-api-15 -u autophone-mochitest-media -t none --artifact

Blake, John: I understand that you are interested in working on media issues on Fennec.
tracking-fennec: --- → ?
(In reply to Bob Clary [:bc:] from comment #7)
> try commit message to run Mm on autophone:
> 
> try: -b do -p android-api-15 -u autophone-mochitest-media -t none --artifact
> 
> Blake, John: I understand that you are interested in working on media issues
> on Fennec.
Definitely!
Thanks for firing so many bugs related to Fennec media test cases. 
May I know what you are planning to do?
Blake,

My ultimate goal is to support the developers of Fennec in finding and fixing all of the bugs which can be exposed through our existing tests. I want Fennec to win and win big and for it to gain acceptance in the marketplace. We need to fix our bugs to accomplish that.

In order to find the bugs our tests would expose if they were actually running, I am trying to get as many of the tests suites as I can support in Autophone running in production.

Initially, I am disabling tests in order to get the tests to run without failure. Once the test is running in production with mostly green results, I intend to perform try runs with sets of the disabled tests enabled in order to find the failures caused by those tests. Once I have the failures specific to that set of disabled tests, I intend to either annotate any existing bugs which are implicated or file new bugs if we don't already have them on file. When the bugs are fixed and those tests are green they can be re-enabled and run in production.

snorp suggested that I cc you and John on the bugs I file as you were interested in fixing media related issues.
tracking-fennec: ? → +
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: