New issue
Advanced search Search tips

Issue 720539 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Web Audio WPT tests

Project Member Reported by rtoy@chromium.org, May 10 2017

Issue description

Look into the web audio WPT tests and figure out why we fail them and fix them or fix the tests (upstream) if they are wrong.

This is the first step in getting Chrome webaudio layout tests upstreamed; we need to know what the existing tests do.
 

Comment 1 by rtoy@chromium.org, May 31 2017

As of today, these are the only failing tests.

Timeout:
retrospective-exponentialRampToValueAtTime.html
retrospective-linearRampToValueAtTime.html
retrospective-setTargetAtTime.html
retrospective-setValueAtTime.html
retrospective-setValueCurveAtTime.html

This is probably a bug in Chrome where we're probably collecting the onaudioprocess callback too soon.  These tests ought to be rewritten not to use a ScriptProcessorNode anyway.


There are a couple more failures, but these are bugs in the tests themselves:

curve-tests.html
mediaElementAudioSourceToScriptProcessorTest.html
test-constantsourcenode.html

Comment 2 by rtoy@chromium.org, Aug 3 2017

Status: WontFix (was: Available)
The retrospective-* tests do simple tests that the automations do the right thing.  Not quite sure how this works because it uses the automation on two different gain nodes to verify that they produce the expected output.

The existing Chrome tests cover these automations much more completely and also very the automation implementation against a reference JS implementation based on the formulas from the spec.

Hence, closing this as wontfix.  When the chrome tests are uploaded, we'll replace the existing tests with the chrome ones because they have better coverage.

Sign in to add a comment