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

Issue 620193 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

testOpeningSettingsDoesntEnableSync flakes in the commit queue

Project Member Reported by hush@chromium.org, Jun 15 2016

Issue description

This test failed once. And passed when I retry the cq.
The logcat link is https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/87623/steps/chrome_sync_shell_test_apk%20%28with%20patch%29%20on%20Android/logs/stdio

I  111.452s Main  1 failed tests remain.
C  111.453s Main  ********************************************************************************
C  111.453s Main  Detailed Logs
C  111.453s Main  ********************************************************************************
C  111.453s Main  [FAIL] org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest#testOpeningSettingsDoesntEnableSync:
C  111.453s Main  java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
C  111.454s Main  	at android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1323)
C  111.454s Main  	at android.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1341)
C  111.454s Main  	at android.app.BackStackRecord.commitInternal(BackStackRecord.java:597)
C  111.454s Main  	at android.app.BackStackRecord.commit(BackStackRecord.java:575)
C  111.454s Main  	at org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest.closeFragment(SyncCustomizationFragmentTest.java:606)
C  111.454s Main  	at org.chromium.chrome.browser.sync.SyncCustomizationFragmentTest.testOpeningSettingsDoesntEnableSync(SyncCustomizationFragmentTest.java:130)
C  111.454s Main  	at java.lang.reflect.Method.invokeNative(Native Method)
C  111.454s Main  	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
C  111.454s Main  	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
C  111.454s Main  	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
C  111.454s Main  	at org.chromium.chrome.test.ChromeActivityTestCaseBase.runTest(ChromeActivityTestCaseBase.java:765)
C  111.454s Main  	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
C  111.454s Main  	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
C  111.454s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
C  111.454s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
C  111.454s Main  	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
C  111.454s Main  	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

 
Not really sure why this would be happening immediately after the fragment was created. I thought it might be something to do with not using getSupportFragmentManager() instead of getFragmentManager(), but PreferenceFragment doesn't inherit from the support version of Fragment so I just... can't use the support one.
Labels: Sync-Code-Health
Components: Services>Sync
Labels: -Sync-Code-Health Hotlist-CodeHealth
Status: WontFix (was: Assigned)
Closing the flaky bugs assigned to me as WontFix as I am leaving Chrome. If these are still occurring please go through the sync triage process again.

Sign in to add a comment