Closed
Bug 1438628
Opened 6 years ago
Closed 6 years ago
[wpt-sync] PR 9548 - Fix WebAudio WPT tests that timeout.
Categories
(Core :: Web Audio, defect, P2)
Core
Web Audio
Tracking
()
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
Details
(Whiteboard: [wptsync downstream])
- AudioParam IDL test: Actually add the IDL to the test. Also removed unused helpers.js. - MediaElementAudioSourceNode Fix error because the expected result is mono, so only has one channel. However, this still fails on bots because there's no audio hardware to drive the online context. Bug: 626703 Test: the-audioparam-interface/idl-test.html Change-Id: I987ad1219da1b6b6ef677f2923416634fa281d5f Reviewed-on: https://chromium-review.googlesource.com/920261 WPT-Export-Revision: 9be702fe44545550b37ac803ba70df6997160269
Reporter | ||
Updated•6 years ago
|
Component: web-platform-tests → Web Audio
Product: Testing → Core
Reporter | ||
Comment 1•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=7cb7d7f6ef978c1d8238085e67aa750207031bba
Reporter | ||
Comment 2•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=c90f51c393238014e91ce73e77d375e7d8950414
Comment 3•6 years ago
|
||
Alex, would you mind doing a first pass triage on this?
Rank: 18
Flags: needinfo?(achronop)
Priority: -- → P2
Comment 4•6 years ago
|
||
I can apply the patch. In addition to that we need not to wait for timeout anymore. Thanks.
Assignee: nobody → achronop
Flags: needinfo?(achronop)
Updated•6 years ago
|
Assignee: achronop → nobody
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/f1eac8f6e796 [wpt PR 9548] - Fix WebAudio WPT tests that timeout., a=testonly
Comment 6•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f1eac8f6e796
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in
before you can comment on or make changes to this bug.
Description
•