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

Issue 849556 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
OOO until 2019-01-24
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug

Blocking:
issue 844815



Sign in to add a comment

"DecodeVariations/VideoDecodeAcceleratorParamTest.TestSimpleDecode/1" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 5 2018

Issue description

"DecodeVariations/VideoDecodeAcceleratorParamTest.TestSimpleDecode/1" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyTgsSBUZsYWtlIkNEZWNvZGVWYXJpYXRpb25zL1ZpZGVvRGVjb2RlQWNjZWxlcmF0b3JQYXJhbVRlc3QuVGVzdFNpbXBsZURlY29kZS8xDA.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

This flaky test/step was previously tracked in  issue 685835 .
 
 Issue 849557  has been merged into this issue.
Cc: mgiuca@chromium.org
Labels: OS-Windows
Owner: kbr@chromium.org
Status: Fixed (was: Untriaged)
This was fixed in r564133. The failures (not really flaky; it was pretty much 100% fail) stopped after this point.

Note that this cycled green about 11 hours before TryFlakes reported this issue :(. Discussed on  Issue 849571 .

Comment 3 by kbr@chromium.org, Jun 5 2018

Blocking: 844815
Sorry for the original breakage – I realized my CL didn't run the affected tryserver, and if I'd been paying more attention, I'd have added it manually to the Cq-Include-Trybots.

Let me link this to the other bug.

Sign in to add a comment