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

Issue 899989 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug
Flaky-Test: org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest#testPassphraseCreation



Sign in to add a comment

org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest#testPassphraseCreation is flaky

Project Member Reported by Findit, Oct 29

Issue description

 Issue 899990  has been merged into this issue.
Also org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest#testPaymentsIntegrationCheckboxEnablesPaymentsIntegration.

Both fail with:
java.lang.AssertionError: Deferred startup never completed
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:92)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:171)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:210)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:222)
	at org.chromium.chrome.test.ChromeActivityTestRule.startMainActivityFromIntent(ChromeActivityTestRule.java:440)
	at org.chromium.chrome.test.ChromeActivityTestRule.startMainActivityWithURL(ChromeActivityTestRule.java:394)
	at org.chromium.chrome.test.ChromeActivityTestRule.startMainActivityOnBlankPage(ChromeActivityTestRule.java:402)
	at org.chromium.chrome.browser.sync.SyncTestRule.startMainActivityForSyncTest(SyncTestRule.java:101)
	at org.chromium.chrome.browser.sync.SyncTestRule$7.evaluate(SyncTestRule.java:222)
	at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(ChromeActivityTestRule.java:124)
	at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55)
	at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:270)
	at org.chromium.chrome.browser.sync.SyncTestRule$8.evaluate(SyncTestRule.java:258)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:237)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:48)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.chromium.base.test.BaseJUnit4ClassRunner.run(BaseJUnit4ClassRunner.java:220)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
	at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(BaseChromiumAndroidJUnitRunner.java:125)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)


Components: Tests>Flaky Services>Sync
Labels: OS-Android
Owner: mastiz@chromium.org
mastiz@, please take a look!
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 30

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

commit 1e22c5ed1838f60b0ab224fa03b2233221661ca7
Author: Ioana Pandele <ioanap@chromium.org>
Date: Tue Oct 30 17:36:10 2018

Disable flaky test cases in SyncCustomizationFragmentTest on KitKat

TBR=mastiz@chromium.org

Bug:  899989 
Change-Id: Ic839d6c9e02caf9f7d74cfd9fadedb7f144d2901
Reviewed-on: https://chromium-review.googlesource.com/c/1307446
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Cr-Commit-Position: refs/heads/master@{#603946}
[modify] https://crrev.com/1e22c5ed1838f60b0ab224fa03b2233221661ca7/chrome/android/sync_shell/javatests/src/org/chromium/chrome/browser/sync/SyncCustomizationFragmentTest.java

Labels: -Sheriff-Chromium
Status: Assigned (was: Untriaged)
Mergedinto: 879246
Status: Duplicate (was: Assigned)

Sign in to add a comment