Joel landed bug 1143218 on inbound today, which changed the Android mochitest chunking around a bit (got the mochitest-gl tests out of the mochitest-plain runs), and since that push, test_mediaElementAudioSourceNodePassThrough.html has been nearly perma-timeout. In order to get the trees open again, I'm disabling the test until it can be fixed.
Whiteboard: [test disabled on Android][leave open]
https://hg.mozilla.org/integration/mozilla-inbound/rev/e13f21ac6d83 This test started timing out once the other test got disabled as well.
Summary: Re-enable test_mediaElementAudioSourceNodePassThrough.html on Android when it isn't extremely timeout-prone → Re-enable test_mediaElementAudioSourceNodePassThrough.html and test_mediaStreamAudioDestinationNode.html on Android when it isn't extremely timeout-prone
Paul, any chance you could take a look at this, please? Thanks!
Flags: needinfo?(ehsan) → needinfo?(padenot)
Just pushed to try with the two test disabling backed out, and logging: https://treeherder.mozilla.org/#/jobs?repo=try&revision=346632734e9a
Assignee: nobody → padenot
Hrm, it's not clear there is a problem here (see the try push in comment 5)? Do I miss a special changeset or something ?
Very likely, something else landed in the mean time to change the chunk boundaries around and make this go away. Fun. If you want to reproduce this with logging, you're probably best off reverting to a known-bad revision first. (My concern being that leaving this latent bug sitting around only means we'll likely see it again at some point)
Should we do a try run with this re-enabled?
Priority: -- → P3
The above try did not have enough chunks running, this should be better: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0beca96bb135
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.