New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 822710 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Bug



Sign in to add a comment

Reduce runtime in AudioInputController unittests

Project Member Reported by marinaciocea@chromium.org, Mar 16 2018

Issue description

Cc: solenberg@chromium.org
Components: Internals>Media>Audio
Labels: Hotlist-GoodFirstBug OS-Android OS-Chrome OS-Fuchsia OS-Linux OS-Mac OS-Windows
Status: Available (was: Untriaged)
Some more tests which could use a speedup: AudioOutputDelegateTest.Error (1000 ms), MojoRendererTest.GetMediaTime (1500 ms), PipelineIntegrationTest.PlaybackWithAudioTrackDisabledThenEnabled (2900 ms, but maybe it just takes that long, it's an integration test after all), AudioRendererMixerBehavioralTest.MixerPausesStream/0 (1200 ms). There are also tests that use fake streams (like AudioOutputResamplerTest.* and many others) which could be reduced by using mock time.

For reference, I wrote https://chromium-review.googlesource.com/c/chromium/src/+/962446 earlier.

This could be good work for someone to learn about tasks, run loops, et c.

Sign in to add a comment