New issue
Advanced search Search tips

Issue 787314 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Blocking:
issue 737802



Sign in to add a comment

AudioOutputTest.Play200HzTone failing on physical GPU bots

Project Member Reported by kbr@chromium.org, Nov 21 2017

Issue description

Failure seen here:
https://ci.chromium.org/buildbot/tryserver.chromium.win/win_optional_gpu_tests_rel/17471

I just restarted the chromium.gpu.fyi waterfall so can't link to other builds, but I think it's failing consistently on other machines too.

[ RUN      ] AudioOutputTest.Play200HzTone
[1936:1488:1120/213733.972:36924219:WARNING:audio_low_latency_output_win.cc(196)] Using WASAPI output with a non-optimal buffer size, glitches from back to back shared memory reads and partial fills of WASAPI output buffers may occur.  Buffer size of 4410 is not an even divisor of 441
../../media/audio/audio_output_unittest.cc(100): error: Expected: (source.callbacks()) >= (1), actual: 0 vs 1
[  FAILED  ] AudioOutputTest.Play200HzTone (396 ms)

 
Owner: sergeyu@chromium.org
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
The change was reverted

Comment 3 by kbr@chromium.org, Nov 21 2017

Blocking: 737802
Cc: jmad...@chromium.org
Please provide more details when updating a bug in this way.

The original change causing the unit test failure was f966ce658c85b635347b89f3812ddcab500d3180 and it was reverted in 133582909af148b44fc286c887b0133161e97dea per  Issue 737802 .

Sign in to add a comment