veyron_speed failing on video_ChromeRTCHWEncodeUsed |
|||||||
Issue descriptionPaladins failed the same test 4 times: https://uberchromegw.corp.google.com/i/chromeos/waterfall?show=veyron_speedy-paladin https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/68896184-chromeos-test/chromeos4-row4-rack11-host4/debug/ AUTOTEST_STATUS::START ---- ---- timestamp=1467996011 localtime=Jul 08 09:40:11 07/08 09:40:12.705 INFO | server_job:0128| START ---- ---- timestamp=1467996011 localtime=Jul 08 09:40:11 07/08 09:40:12.889 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: START video_ChromeRTCHWEncodeUsed video_ChromeRTCHWEncodeUsed timestamp=1467996011 localtime=Jul 08 09:40:11 07/08 09:40:12.890 INFO | server_job:0128| START video_ChromeRTCHWEncodeUsed video_ChromeRTCHWEncodeUsed timestamp=1467996011 localtime=Jul 08 09:40:11 07/08 09:40:36.600 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: ERROR video_ChromeRTCHWEncodeUsed video_ChromeRTCHWEncodeUsed timestamp=1467996035 localtime=Jul 08 09:40:35 Cannot find Media.RTCVideoEncoderInitEncodeSuccess histogram. 07/08 09:40:36.601 INFO | server_job:0128| ERROR video_ChromeRTCHWEncodeUsed video_ChromeRTCHWEncodeUsed timestamp=1467996035 localtime=Jul 08 09:40:35 Cannot find Media.RTCVideoEncoderInitEncodeSuccess histogram. 07/08 09:40:36.628 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: END ERROR video_ChromeRTCHWEncodeUsed video_ChromeRTCHWEncodeUsed timestamp=1467996035 localtime=Jul 08 09:40:35 07/08 09:40:36.629 INFO | server_job:0128| END ERROR video_ChromeRTCHWEncodeUsed video_ChromeRTCHWEncodeUsed timestamp=1467996035 localtime=Jul 08 09:40:35
,
Jul 8 2016
All the failed test runs were on http://cautotest/afe/#tab_id=view_host&object_id=1889 But it ran other tests fine. I really suspect a bug in ToT.
,
Jul 8 2016
Huh, we saw similar failures yesterday, which we thought were flake, see https://bugs.chromium.org/p/chromium/issues/detail?id=541408
,
Jul 8 2016
emircan, could this be related to Reland "Use kEnableWebRtcHWH264Encoding flag when SW fallback is available" https://codereview.chromium.org/2125163003 ?
,
Jul 8 2016
Its failing on release builders too: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=68879216 So it is a bug in ToT.
,
Jul 8 2016
That patch turns on HW H264 encoding for these devices, which works with real use-cases(AppRTC loopback). Maybe we need to change something in tests now to handle this newly enabled feature? wuchengli@ and posciak@ can you PTAL as well.
,
Jul 8 2016
vsuley@ disabled this test for arc yesterday in issue 541408 for the similar error that failed cheets bots.
,
Jul 8 2016
There is an easy way to check if https://codereview.chromium.org/2125163003 is the reason it broke. If you disable WebRTC-H264WithOpenH264FFmpeg feature and run the tests, it should mimic the behavior before the test. https://cs.chromium.org/chromium/src/content/public/common/feature_h264_with_openh264_ffmpeg.cc?rcl=0&l=11
,
Jul 8 2016
I cannot reach vsuley@, but if anyone has veyron_speedy device, you can try running the test with --disable-features=WebRTC-H264WithOpenH264FFmpeg to verify if the above CL is the reason.
,
Jul 8 2016
vsuley@ disabled the .arc test as the initial thought was that this is a test flake but looks like it's a regression. The non-arc test is still running and that's the test is still running on veyron_speedy.
,
Jul 8 2016
This seems to be same as chromium:541408. Manually investigating revealed that chrome://histograms/Media.RTC is not showing the "Media.RTCVideoEncoderInitEncodeSuccess" & "Media.RTCVideoEncoderProfile" histograms, both of which the test relies on for validation. Disabling the "WebRTC H.264 Software video encoder/decoder" did not fix it. Btw, I'm using this page for creating a test streaming connection: https://apprtc.appspot.com/?debug=loopback&vsc=vp8
,
Jul 8 2016
,
Jul 9 2016
The regression started at R54-8562.0.0 / 54.0.2790.0. https://codereview.chromium.org/2125163003 was picked up at 8564.0.0 / 54.0.2791.0. So it's not that.
,
Jul 11 2016
Speedy is all green for the last 24 builds. Could somebody update the status? Is it fixed? |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sbasi@chromium.org
, Jul 8 2016