audio_CrasLoopback failing: Timeout waiting active stream count to become 0 |
|||||
Issue description
audio_CrasLoopback is failing intermittently on boards like elm, veyron_jerry, asuka, banon, butterfly, cave, nyan_big, peach_pit, squawks, and stout.
The error is "Timeout waiting active stream count to become 0".
cras_utils.capture(noise_file, duration=1)
self.wait_for_active_stream_count(0)
I reproduced the issue on elm. cras_test_client capturing worked fine. The problem was there was another active stream while testing. That active stream is never closed. Jimmy. Is that expected?
# cras_test_client --dump_s
System Volume (0-100): 100
Capture Gain (0.00 - 0.00): 0.00dB
User muted: Not muted
Output Devices:
ID Name
8 mtk-rt5650: :0,2
6 mtk-rt5650: :0,0
Output Nodes:
Stable Id ID Vol Plugged L/R swapped Time Hotword Type Name
(1853bfca) 8:0 100 no no 0 HDMI mtk-rt5650 HDMI Jack
(9e934263) 6:0 100 yes no 1508549600 HEADPHONE *Headphone
(72a57953) 6:1 100 yes no 1508549600 INTERNAL_SPEAKER Speaker
Input Devices:
ID Name
7 mtk-rt5650: :0,1
5 Post DSP Loopback
4 Post Mix Pre DSP Loopback
Input Nodes:
Stable Id ID Gain Plugged L/R swapped Time Hotword Type Name
(1d13c3f3) 7:0 0 yes no 1508549601 MIC *Mic
(30b0c661) 7:1 0 yes no 1508549601 INTERNAL_MIC Internal Mic
(8c74f766) 5:0 0 yes no 0 POST_DSP_LOOPBACK Post DSP Loopback
(8a04af91) 4:0 0 yes no 0 POST_MIX_LOOPBACK Post Mix Pre DSP Loopback
Attached clients:
ID pid uid
10 23884 0
11 23884 0
22 26101 0
Num active streams: 1
Last audio active time: 1304, 101445534
,
Oct 28 2017
Do these tests need chrome running? Checking the number of streams with either android or chrome active will always lead to flaky tests.
,
Oct 28 2017
Great point. Let me nuke chrome in autotest instead.
,
Nov 3 2017
Now I'm suspecting the active stream was caused by previous runs of audio tests. If loopback_latency hangs, num of active stream will remain 1. https://bugs.chromium.org/p/chromium/issues/detail?id=779936
,
Nov 3 2017
I believe some failures will be gone after 779936 is fixed. Let's revisit after 779936 is fixed.
,
Nov 6 2017
Confirmed this is fixed by 779936. elm failed audio_AlsaLoopback in 10096 and passed 10099.
,
Nov 17 2017
,
Nov 17 2017
Still observing some failures randomly on different devices: https://stainless.corp.google.com/search?view=matrix&row=board&col=build&first_date=20171111&last_date=20181117&test=audio_CrasLoopback&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true these failures are followed in https://bugs.chromium.org/p/chromium/issues/detail?id=783534 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by wuchengli@chromium.org
, Oct 27 2017