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

Issue 859616 link

Starred by 1 user
Status: Duplicate
Owner:
jkrcal@chromium.org
Closed: Oct 1
Cc:
bsazonov@chromium.org
treib@chromium.org
mastiz@chromium.org
█ tschumann@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

"org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest#testOpeningSettingsDoesntStartEngine" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 2 
"org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest#testOpeningSettingsDoesntStartEngine" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNybgsSBUZsYWtlImNvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIuc3luYy5TeW5jQ3VzdG9taXphdGlvbkZyYWdtZW50VGVzdCN0ZXN0T3BlbmluZ1NldHRpbmdzRG9lc250U3RhcnRFbmdpbmUM.

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
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 2 

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

commit 9033c46f14b0f52c5a5bb26e0ab07ffacb3b0d88
Author: spqchan <spqchan@chromium.org>
Date: Mon Jul 02 21:04:44 2018

Disable flaky SyncCustomizationFragmentTest tests

TBR=carlosk@chromium.org

Bug:  859616 ,  859617 ,  859615 
Change-Id: Ibc6fd6db390a7e3a42dd9cc929efb7a079ac9a37
Reviewed-on: https://chromium-review.googlesource.com/1123222
Reviewed-by: Sarah Chan <spqchan@chromium.org>
Commit-Queue: Sarah Chan <spqchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571996}
[modify] https://crrev.com/9033c46f14b0f52c5a5bb26e0ab07ffacb3b0d88/chrome/android/sync_shell/javatests/src/org/chromium/chrome/browser/sync/SyncCustomizationFragmentTest.java

Comment 2 by spqc...@chromium.org, Jul 2

Owner: bsazonov@chromium.org
Status: Assigned (was: Untriaged)
Assigning to bsazonov@ to investigate

Comment 3 by lucmult@chromium.org, Jul 3

Labels: -Sheriff-Chromium Test-Disabled
Removing from sheriff queue.

Comment 4 by bsazonov@chromium.org, Jul 3

Cc: bsazonov@chromium.org
Components: Services>Sync
Labels: OS-Android
Owner: treib@chromium.org
My recent CL hasn't changed the behavior of SyncCustomizationFragment & these tests were flaky before my CL.

Reassigning to Sync team. Marc, can you please take a look?

Comment 5 by treib@chromium.org, Jul 3

Cc: treib@chromium.org
Owner: jkrcal@chromium.org
This looks similar to  bug 859615  and  bug 859617 , but in contrast to those, it apparently became flaky only recently. Assigning to our current oncall to take a look.

Comment 6 by mastiz@chromium.org, Jul 30 

Triage ping, thanks!

Comment 7 by jkrcal@chromium.org, Aug 6 

I am sorry, I probably won't make it this week and I am OOO afterwards until Aug 28.

Comment 8 by jkrcal@chromium.org, Aug 6

Labels: -Pri-1 Pri-2
Thinking about my message, down-grading this bug to prio=2 to make it consistent with my availability.

If you disagree, please flip it back to prio=1 and I try to look at this this week / look for someone else.

Comment 9 by melandory@chromium.org, Sep 9 

sync-triage-ping, any updates?

Comment 10 by mastiz@chromium.org, Oct 1

Mergedinto: 879246
Status: Duplicate (was: Assigned)
►

Sign in to add a comment