Issue metadata
Sign in to add a comment
|
video_ChromeHWDecodeUsed.h264 / vp9 regressed between CrOS 11067-11071. |
||||||||||||||||||||||
Issue descriptionhttps://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/testDetails?milestone=71&daysBack=30&testName=video_ChromeHWDecodeUsed.h264.mse https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/testDetails?milestone=71&daysBack=30&testName=video_ChromeHWDecodeUsed.vp9.mse Mostly x86_64 families are affected in video_ChromeHWDecodeUsed.h264 and some x86_64 boards are affected in video_ChromeHWDecodeUsed.vp9. Regression range from CrOS 11067.0.0 to 11071.0.0. All became green starting from 11072.0.0. The error is that the test failed to observe histogram difference on histograms/Media.GpuVideoDecoderInitializeStatus . (0 status count didn't increase for about ten retries.) Finding culprit CL. noted that from 11071.0.0 to 11072.0.0 (bad to good), Chrome version are the same. So culprit is unlikely in Chrome repository.
,
Sep 17
Suspect cras issue. Verifying.
,
Sep 19
Bisect and found https://chromium-review.googlesource.com/c/chromiumos/third_party/adhd/+/1226926 fixed the regression
,
Sep 19
I'm curious. Did you bisect manually or use bisect tools?
,
Sep 21
https://chromium-review.googlesource.com/c/chromiumos/third_party/adhd/+/1180782 was the culprit and https://chromium-review.googlesource.com/c/chromiumos/third_party/adhd/+/1226926 fixed the regression. While I set up bisect tool env, I ran test against 11071 and 11072 and found cras has crash issue on 11071. So I manually looking into cras related issues to do manual bisect. It took long to confirm the above finding as it took more than 30 minutes to cros flash to a lab machine and I got only fragment time bisecting during vacation. I would see if bisect tool can work well on this case.
,
Oct 3
Issue 891415 has been merged into this issue.
,
Oct 8
as per https://stainless.corp.google.com/search?view=matrix&row=model&col=build&first_date=2018-10-02&last_date=2018-10-08&test=video_ChromeHWDecodeUsed&build=R71-*&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false
,
Oct 9
Wu-cheng, I tried using bisect-kit to find culprit CL and found some issue. Asking Kuang-che to investigate: crbug.com/893441
,
Oct 9
Remove some cc who were mistakenly added because I set the wrong duplicate issue.
,
Oct 12
According to the healthmonitor dashboard, the regression is between 11066.0.0 and 11067.0.0 and it's not flaky. However, I don't know why my local build 11066.0.0 failed with the same error message as well. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by deanliao@chromium.org
, Sep 17