Issue metadata
Sign in to add a comment
|
video_VideoSanity / video_ChromeHWDecodeUsed / video_ChromeRTCHWDecodeUsed on arm chrome PFQs: (daisy_skate, peach_pit, veyron_minnie-cheets |
||||||||||||||||||||||
Issue descriptionHuman readable form of issue 599172. An example: https://chromegw.corp.google.com/i/chromeos/builders/daisy_skate-chrome-pfq/builds/2457/steps/HWTest%20%5Bbvt-cq%5D/logs/stdio has failures: video_ChromeHWDecodeUsed [ FAILED ] video_ChromeHWDecodeUsed FAIL: Unhandled unicode: Unhandled DevtoolsTargetCrashException: Devtools target crashed video_VideoSanity [ FAILED ] video_VideoSanity FAIL: Unhandled unicode: Unhandled DevtoolsTargetCrashException: Devtools target crashed video_VideoSanity [ PASSED ] video_ChromeHWDecodeUsed [ FAILED ] video_ChromeHWDecodeUsed ERROR: Media.GpuVideoDecoderInitializeStatus not loaded or histogram bucket not found or histogram bucket found at < 100% video_ChromeHWDecodeUsed [ FAILED ] video_ChromeHWDecodeUsed FAIL: Unhandled unicode: Unhandled DevtoolsTargetCrashException: Devtools target crashed video_VideoSanity [ FAILED ] video_VideoSanity FAIL: Unhandled unicode: Unhandled DevtoolsTargetCrashException: Devtools target crashed video_ChromeRTCHWDecodeUsed [ FAILED ] video_ChromeRTCHWDecodeUsed FAIL: Unhandled DevToolsClientConnectionError: [Errno 104] Connection reset by peer video_ChromeHWDecodeUsed [ FAILED ] video_ChromeHWDecodeUsed ERROR: Media.GpuVideoDecoderInitializeStatus not loaded or histogram bucket not found or histogram bucket found at < 100% looks like perhaps something in chrome between 53.0.2751.0 & 53.0.2752.0 Or Chrome OS R53-8387.0.0-rc1 & R53-8388.0.0-rc1
,
May 31 2016
These canaries have been red since: May 29 20:25 ?? failure #2457 Failed steps failed cbuildbot [daisy_skate-chrome-pfq] failed hwtest [bvt-cq] May 29 20:25 ?? failure #2106 Failed steps failed cbuildbot [peach_pit-chrome-pfq] failed hwtest [sanity] May 29 20:25 ?? failure #233 Failed steps failed cbuildbot [veyron_minnie-cheets-chrome-pfq] failed hwtest [sanity] Ignore veyron_rialto (it is failing build_packages due to issue 615730 ).
,
May 31 2016
,
May 31 2016
,
May 31 2016
Looks like crrev.com/1ace3b00d9dad163255b8e73deaad53c0a43a79a is causing an out-of-bounds vector access: terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) I'm not sure what's the root cause yet, but I confirmed reverting fixes this and video works after the revert, so I'd recommend reverting and we can investigate further afterwards.
,
May 31 2016
Revert in CQ: https://codereview.chromium.org/2019333004/
,
May 31 2016
CL:2019333004 landed as https://crrev.com/f22b1b6d4d903ba1640c942c70cd6e95ff8a03f5 Cr-Commit-Position: refs/heads/master@{#396812}
,
Jun 1 2016
Revert should be in 53.0.2754.0
,
Jun 1 2016
All three builders are now testing 53.0.2754.0. Fingers crossed... https://chromegw.corp.google.com/i/chromeos/builders/veyron_minnie-cheets-chrome-pfq/builds/241 https://chromegw.corp.google.com/i/chromeos/builders/daisy_skate-chrome-pfq/builds/2465 https://chromegw.corp.google.com/i/chromeos/builders/peach_pit-chrome-pfq/builds/2114
,
Jun 1 2016
All three chrome-pfq in #9 are green. Whoot! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by djkurtz@chromium.org
, May 31 2016