New issue
Advanced search Search tips

Issue 621760 link

Starred by 2 users
Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"org.chromium.content.browser.TracingControllerAndroidTest#testTraceFileCreation" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 21 2016 
"org.chromium.content.browser.TracingControllerAndroidTest#testTraceFileCreation" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyWgsSBUZsYWtlIk9vcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLlRyYWNpbmdDb250cm9sbGVyQW5kcm9pZFRlc3QjdGVzdFRyYWNlRmlsZUNyZWF0aW9uDA.

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 vasi...@chromium.org, Jun 21 2016

Labels: -Sheriff-Chromium Infra-Trooper
I  224.038s run_tests_on_device(0384884f0ae5848c)    Failure in testTraceFileCreation:
I  224.038s run_tests_on_device(0384884f0ae5848c)    junit.framework.AssertionFailedError
I  224.038s run_tests_on_device(0384884f0ae5848c)    	at org.chromium.content.browser.TracingControllerAndroidTest.testTraceFileCreation(TracingControllerAndroidTest.java:62)
I  224.038s run_tests_on_device(0384884f0ae5848c)    	at java.lang.reflect.Method.invokeNative(Native Method)
I  224.038s run_tests_on_device(0384884f0ae5848c)    	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
I  224.038s run_tests_on_device(0384884f0ae5848c)    	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
I  224.038s run_tests_on_device(0384884f0ae5848c)    	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at org.chromium.content_shell_apk.ContentShellTestBase.runTest(ContentShellTestBase.java:233)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
I  224.039s run_tests_on_device(0384884f0ae5848c)    	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

The line is
assertTrue(file.exists());

Can it be a device problem?
►

Sign in to add a comment