New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 875910 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 875699
Owner:
Closed: Aug 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

PFQ failing since 70.3525.0, BVT test failure with peach-pit

Project Member Reported by geo...@google.com, Aug 20

Issue description

Chrome PFQ is failing on peach-pit BVT, likely related to crbug/845372

Error:

Test	Results	Reason	Sponge	Autotest	Health	Stainless
peach_pit-chrome-pfq/R70-10977.0.0-rc1/bvt-cq/video_ChromeRTCHWDecodeUsed/video_ChromeRTCHWDecodeUsed.vp8

Expect Media.RTCVideoDecoderInitDecodeSucces has 1. Histogram: {}

This change seems to the reason:
 https://crrev.com/c/1177402 cros/video: use HistogramDiffer to expect histogram change

Based on changelog, this seems to line up with the failures appearing.
https://crosland.corp.google.com/log/10975.0.0..10977.0.0
 
Cc: jen...@chromium.org
Labels: Build-PFQ-Failures
This issue has caused both informational build and master PFQ failure.
Cc: updowndota@chromium.org
deanliao@, I saw your cl to revert the one that caused the failure, but the cl is not landed yet. This issue is blocking our pfq, would you please let me know when the fix will be landed? Many thanks!
Status: Assigned (was: Untriaged)
Looks like https://crrev.com/c/1177402 should have been reverted by:
https://crrev.com/c/1180791


Also, I see there is another cl retrying to reland the original one:
https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1180792/4

deanliao@, would you please update the status in this bug? Thanks!


Cc: hiroh@chromium.org
The previous CL contains a bit mistake. So we had reverted it, and fixed it. I am submitting it again.
I think the currently submitting CL, crrev.com/c/1180792, will not break anything in CQ/PFQ.
Re#8, thanks a lot for the update and fixing the issue. I will keep an eye on the bots when they pick it up.
Yes, the cl fixed the issue. It was picked up by peach_pit-chrome-pfq build in build 2863937, and had a green run.
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8937612593446405968
Mergedinto: 875699
Status: Duplicate (was: Assigned)

Sign in to add a comment