WebRtcAudioQualityBrowserTests failing on chromium.webrtc Win7 Tester |
||||
Issue description[ADD relevant info inline] Link to build or pfq page. build # for that buildbot. https://build.chromium.org/p/chromium.webrtc/builders/Win7%20Tester/builds/33302 https://build.chromium.org/p/chromium.webrtc/builders/Win7%20Tester/builds/33303 Snippet of log that contains the failure. 4 tests failed: WebRtcAudioQualityBrowserTest.MANUAL_TestAutoGainControlOnLowAudio (e:\b\c\b\win_builder\src\chrome\browser\media\webrtc\webrtc_audio_quality_browsertest.cc:803) WebRtcAudioQualityBrowserTest.MANUAL_TestAutoGainIsOffWithAudioProcessingOff (e:\b\c\b\win_builder\src\chrome\browser\media\webrtc\webrtc_audio_quality_browsertest.cc:810) WebRtcAudioQualityBrowserTest.MANUAL_TestCallQualityWithAudioFromFakeDevice (e:\b\c\b\win_builder\src\chrome\browser\media\webrtc\webrtc_audio_quality_browsertest.cc:683) WebRtcAudioQualityBrowserTest.MANUAL_TestCallQualityWithAudioFromWebAudio (e:\b\c\b\win_builder\src\chrome\browser\media\webrtc\webrtc_audio_quality_browsertest.cc:688) Corresponding bot on chromium.webrtc.fyi is working: https://build.chromium.org/p/chromium.webrtc.fyi/waterfall?builder=Win7%20Tester Maybe an infra issue? No obvious cause in the blamelist.
,
Feb 15 2017
It seems this just happened again: https://build.chromium.org/p/chromium.webrtc/builders/Win7%20Tester/builds/33327
,
Feb 17 2017
Seems to be fine again.
,
Feb 20 2017
Do we really intend to leave this as it is? Looking at https://build.chromium.org/p/chromium.webrtc/builders/Win7%20Tester?numbuilds=200, the bot/test seems to be flaking heavily.
,
Feb 20 2017
Well. It has happened before and a lot of time has gone into investigating it. Since this test might be affected by other Chrome changes we cannot (and shouldn't) spend too much time on it if we don't know it's a WebRTC issue. That way I'm willing to "give it some time" when this happens, as it has recovered several times before: * bug 681577 * bug 677256 * bug 672811 Long term, we probably should consider removing the test entirely instead, or spend time on making it more robust (but for that we need to know what's causing the failures). Adding more logging would be one option start with. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kjellander@chromium.org
, Feb 14 2017