New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 3 users
Status: Assigned
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug

Sign in to add a comment
"" is flaky
Project Member Reported by, Apr 19 2017 Back to list
"" 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 11 recent flakes. List of all flakes can be found at

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here:
Labels: OS-Android
Status: Assigned
Assigning to the feature owner, and disabling in the meantime.
Comment 2 by, Apr 19 2017
Labels: -Sheriff-Chromium
Removing Sheriff-Chromium label since the test was disabled.
Comment 3 by, Apr 19 2017
Disabling patch had the wrong bug number. Was disabled in
Comment 4 Deleted
testValid is also flakey. Disabling this test as well. Seems to have been introduced in the same CL so it's probably got the same cause.
Project Member Comment 7 by, Apr 21 2017
Project Member Comment 8 by, Jul 12
The following revision refers to this bug:

commit 0982cbaa2225d8a7a895aebaaed64be032b418a1
Author: wychen <>
Date: Wed Jul 12 05:10:09 2017

Enable all tests in CopylessPasteTest

The following tests are re-enabled:
- testValid
- testNoMeta
- testCache

All flaky failures in CopylessPasteTest are due to timeout in
CallbackHelper.waitForCallback(). Wait for longer to see if it gets


BUG=713172, 713895 , 713878 , 693650 

Cr-Commit-Position: refs/heads/master@{#485865}


 Issue 713895  has been merged into this issue.
 Issue 713878  has been merged into this issue.
According to the dashboard, the failure rate since re-enabling is much lower than last time.

Looks like the hypothesis was right. The test does take longer. I think we can further relax the timeout to make the failure rate even lower.
Project Member Comment 12 by, Jul 20
The following revision refers to this bug:

commit 9ab17245e9677a467e2e53f8ec2e9af874fb6167
Author: Wei-Yin Chen (陳威尹) <>
Date: Thu Jul 20 22:32:55 2017

Use longer timeout for tests in CopylessPasteTest

Increasing timeout (
lowered the failure rate. This indicates the tests are not inherently
flaky. They just run for longer.

Bug: 713172, 747073
Change-Id: I20a039776aa2aa9f70560e8d688f27ef34e6eb6a
Reviewed-by: Ted Choc <>
Commit-Queue: Wei-Yin Chen (陳威尹) <>
Cr-Commit-Position: refs/heads/master@{#488448}

Unfortunately it seems the longer timeout wasn't enough to stop one of the tests turning the Android Tests build red here: :(

Might be worth a @RetryOnFailure ?
Project Member Comment 14 by, Jul 24
The following revision refers to this bug:

commit 6ab04c29c830dde25549fe4ce1d5a4c875296910
Author: Wei-Yin Chen (陳威尹) <>
Date: Mon Jul 24 22:57:12 2017

Add @RetryOnFailure on flaky CopylessPasteTest

This allows more investigation without making bots red.

Bug: 713172
Change-Id: I27e9b49ae816fa743e18ebb6c34931ac733d472a
Reviewed-by: Ted Choc <>
Commit-Queue: Wei-Yin Chen (陳威尹) <>
Cr-Commit-Position: refs/heads/master@{#489117}

 Issue 749370  has been merged into this issue.
Sign in to add a comment