Re-enable test_mediaElementAudioSourceNodePassThrough.html and test_mediaStreamAudioDestinationNode.html on Android when it isn't extremely timeout-prone

NEW
Assigned to

Status

()

P4
normal
4 years ago
a year ago

People

(Reporter: RyanVM, Assigned: padenot)

Tracking

({leave-open})

Trunk
ARM
Android
leave-open
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [test disabled on Android][leave open])

(Reporter)

Description

4 years ago
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.
(Reporter)

Comment 1

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/2f2c17a6a4fa
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
Flags: needinfo?(ehsan)

Comment 4

4 years ago
Paul, any chance you could take a look at this, please?  Thanks!
Flags: needinfo?(ehsan) → needinfo?(padenot)
(Assignee)

Comment 5

4 years ago
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
Flags: needinfo?(padenot)
(Assignee)

Comment 6

4 years ago
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 ?
Flags: needinfo?(ryanvm)
(Reporter)

Comment 7

4 years ago
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)
Flags: needinfo?(ryanvm)
Should we do a try run with this re-enabled?
Flags: needinfo?(padenot)
Priority: -- → P3
(Assignee)

Comment 10

3 years ago
The above try did not have enough chunks running, this should be better:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=0beca96bb135
See Also: → bug 1339448
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.