New issue
Advanced search Search tips

Issue 827449 link

Starred by 2 users
Status: WontFix
Owner:
tedc...@chromium.org
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

"org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest#testHelpPageSkipsFirstRun" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Mar 30 2018 
"org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest#testHelpPageSkipsFirstRun" 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 41 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyYQsSBUZsYWtlIlZvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIuZmlyc3RydW4uRmlyc3RSdW5JbnRlZ3JhdGlvblRlc3QjdGVzdEhlbHBQYWdlU2tpcHNGaXJzdFJ1bgw.

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

Comment 1 by zmin@chromium.org, Apr 3 2018

Labels: OS-Android
 496.890s run_tests_on_device(03a501e8f0e944fe)    Process crashed while executing testHelpPageSkipsFirstRun(org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest):
I  496.890s run_tests_on_device(03a501e8f0e944fe)    android.os.StrictMode$StrictModeViolation: policy=2655 violation=2
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.StrictMode.executeDeathPenalty(StrictMode.java:1377)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.StrictMode.access$1300(StrictMode.java:116)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.StrictMode$AndroidBlockGuardPolicy.handleViolation(StrictMode.java:1370)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.StrictMode$AndroidBlockGuardPolicy$1.run(StrictMode.java:1252)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.Handler.handleCallback(Handler.java:733)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.Handler.dispatchMessage(Handler.java:95)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.os.Looper.loop(Looper.java:136)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at android.app.ActivityThread.main(ActivityThread.java:5001)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at java.lang.reflect.Method.invokeNative(Method.java)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at java.lang.reflect.Method.invoke(Method.java:515)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
I  496.890s run_tests_on_device(03a501e8f0e944fe)    	at dalvik.system.NativeStart.main(NativeStart.java)

Comment 2 by zmin@chromium.org, Apr 3 2018

Labels: -Sheriff-Chromium
Owner: tedc...@chromium.org
Status: Assigned (was: Untriaged)
The test seems stop flaky for now. Assign to Ted for future investigation/triaging.

Comment 3 by tedc...@chromium.org, Jun 5 2018

Status: WontFix (was: Assigned)
Unfortunately, that stack isn't actionable so I'm closing this out.  I couldn't get any of the full logcats to load either to see if there was any more context.  This looks to be a general strict mode violation that isn't directly related to the test at all.
►

Sign in to add a comment