"org.chromium.chrome.browser.customtabs.CustomTabActivityTest#testWarmupAndLaunchRegularChrome" is flaky |
||||
Issue description"org.chromium.chrome.browser.customtabs.CustomTabActivityTest#testWarmupAndLaunchRegularChrome" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyaAsSBUZsYWtlIl1vcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIuY3VzdG9tdGFicy5DdXN0b21UYWJBY3Rpdml0eVRlc3QjdGVzdFdhcm11cEFuZExhdW5jaFJlZ3VsYXJDaHJvbWUM. 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
,
Dec 12 2016
Device(0a9ec79b43e4b97b) 12-12 04:55:56.469 7379 7379 W System.err: java.lang.AssertionError Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.chrome.browser.metrics.UmaUtils.getForegroundStartTime(UmaUtils.java:96) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.chrome.browser.ChromeActivity.postDeferredStartupIfNeeded(ChromeActivity.java:1830) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.chrome.browser.ChromeActivity$4.onPageLoadFinished(ChromeActivity.java:523) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.chrome.browser.tab.Tab.didFinishPageLoad(Tab.java:1683) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.chrome.browser.tab.TabWebContentsObserver.didFinishLoad(TabWebContentsObserver.java:157) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.content.browser.webcontents.WebContentsObserverProxy.didFinishLoad(WebContentsObserverProxy.java:195) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native Method) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:41) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at android.os.Handler.dispatchMessage(Handler.java:102) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at android.os.Looper.loop(Looper.java:136) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at android.app.ActivityThread.main(ActivityThread.java:5001) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at java.lang.reflect.Method.invokeNative(Native Method) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at java.lang.reflect.Method.invoke(Method.java:515) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) Device(0a9ec79b43e4b97b) 12-12 04:55:56.479 7379 7379 W System.err: at dalvik.system.NativeStart.main(Native Method) Device(0a9ec79b43e4b97b) 12-12 04:55:56.489 7379 7379 F chromium: [FATAL:jni_android.cc(243)] Please include Java exception stack in crash report Device(0a9ec79b43e4b97b) 12-12 04:55:56.489 7379 7379 F chromium:
,
Dec 12 2016
This is the same error seen in 673385. Looking for an appropriate owner / possible culprit.
,
Dec 12 2016
,
Dec 13 2016
Detected 3 new flakes for test/step "org.chromium.chrome.browser.customtabs.CustomTabActivityTest#testWarmupAndLaunchRegularChrome". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyaAsSBUZsYWtlIl1vcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIuY3VzdG9tdGFicy5DdXN0b21UYWJBY3Rpdml0eVRlc3QjdGVzdFdhcm11cEFuZExhdW5jaFJlZ3VsYXJDaHJvbWUM. This message was posted automatically by the chromium-try-flakes app.
,
Dec 13 2016
Given the failure pattern, this was probably caused by 673433. If that's the case, we shouldn't see any more flakes in this test. I'll hold this for a day or two and triage appropriately if flakes continue.
,
Dec 14 2016
This flake has not recurred since 673433 was fixed. |
||||
►
Sign in to add a comment |
||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Dec 12 2016