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

Issue 672999 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
OOO until 2019-01-24
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocked on:
issue 671416
issue 672706



Sign in to add a comment

"pixel_test (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Dec 9 2016

Issue description

"pixel_test (with patch)" 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 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIgsSBUZsYWtlIhdwaXhlbF90ZXN0ICh3aXRoIHBhdGNoKQw.



This flaky test/step was previously tracked in  issue 662683 .
 
Owner: kbr@chromium.org
Project Member

Comment 3 by bugdroid1@chromium.org, Dec 13 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e3e722f67a0b233f7291532478516434a6fe3bcb

commit e3e722f67a0b233f7291532478516434a6fe3bcb
Author: nednguyen <nednguyen@google.com>
Date: Tue Dec 13 14:44:34 2016

[gpu_tests] Disable flaky pixel tests

BUG= 672999 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=kbr@chromium.org,zmo@chromium.org

Review-Url: https://codereview.chromium.org/2569013005
Cr-Commit-Position: refs/heads/master@{#438166}

[modify] https://crrev.com/e3e722f67a0b233f7291532478516434a6fe3bcb/content/test/gpu/gpu_tests/pixel_expectations.py

Labels: Tests-Disabled
Project Member

Comment 5 by bugdroid1@chromium.org, Dec 13 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b4d5b9ad484224745b4780b1f828dab6cf0fd9f7

commit b4d5b9ad484224745b4780b1f828dab6cf0fd9f7
Author: kbr <kbr@chromium.org>
Date: Tue Dec 13 20:12:31 2016

Revert of [gpu_tests] Disable flaky pixel tests (patchset #1 id:1 of https://codereview.chromium.org/2569013005/ )

Reason for revert:
These tests failed catastrophically three times on December 9 on Windows and Mac OS. The runs all timed out. If this had been persistent, I'd be worried and would agree with this disabling -- but looking again, they've failed once on December 11 and once on December 12. Disabling them wholesale is unwarranted.

Original issue's description:
> [gpu_tests] Disable flaky pixel tests
>
> BUG= 672999 
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
>
> TBR=kbr@chromium.org,zmo@chromium.org
>
> Committed: https://crrev.com/e3e722f67a0b233f7291532478516434a6fe3bcb
> Cr-Commit-Position: refs/heads/master@{#438166}

TBR=nednguyen@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= 672999 

Review-Url: https://codereview.chromium.org/2569843004
Cr-Commit-Position: refs/heads/master@{#438273}

[modify] https://crrev.com/b4d5b9ad484224745b4780b1f828dab6cf0fd9f7/content/test/gpu/gpu_tests/pixel_expectations.py

Labels: -Tests-Disabled

Comment 7 by kbr@chromium.org, Dec 13 2016

Blockedon: 672706 671416
Status: WontFix (was: Untriaged)
The Mac failure, https://chromium-swarm.appspot.com/task?id=32facb4b13c40d10&refresh=10&show_raw=1 , happened because of a machine misconfiguration that was solved in  Issue 671416 . The machine has already been fixed.

The two Windows failures, https://chromium-swarm.appspot.com/task?id=32fae95fe82dc710&refresh=10&show_raw=1 and https://chromium-swarm.appspot.com/task?id=32fa2a528a916c10&refresh=10&show_raw=1 , happened because of another machine misconfiguration which is being tracked in  Issue 672706 . The machine has been taken out of the Swarming pool and won't cause more problems.

There's no action to take in response to this particular report. Closing as WontFix.

Sign in to add a comment