New issue
Advanced search Search tips

Issue 672623 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocked on:
issue 672382



Sign in to add a comment

"org.chromium.android_webview.test.AwContentsClientShouldInterceptRequestTest#testBaseUrlOfLoadDataSentInRefererHeader" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Dec 8 2016

Issue description

"org.chromium.android_webview.test.AwContentsClientShouldInterceptRequestTest#testBaseUrlOfLoadDataSentInRefererHeader" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNygAELEgVGbGFrZSJ1b3JnLmNocm9taXVtLmFuZHJvaWRfd2Vidmlldy50ZXN0LkF3Q29udGVudHNDbGllbnRTaG91bGRJbnRlcmNlcHRSZXF1ZXN0VGVzdCN0ZXN0QmFzZVVybE9mTG9hZERhdGFTZW50SW5SZWZlcmVySGVhZGVyDA.

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
 
Blockedon: 672382
Labels: -Sheriff-Chromium
The same symptoms as the other tests on android_n5x_swarming_rel:

I  474.020s run_tests_on_device(008c099374eeb8f3)    Error in testBaseUrlOfLoadDataSentInRefererHeader:
I  474.020s run_tests_on_device(008c099374eeb8f3)    java.util.concurrent.TimeoutException: waitForCallback timed out!
I  474.020s run_tests_on_device(008c099374eeb8f3)    	at org.chromium.base.test.util.CallbackHelper.waitForCallback(CallbackHelper.java:183)
I  474.020s run_tests_on_device(008c099374eeb8f3)    	at org.chromium.base.test.util.CallbackHelper.waitForCallback(CallbackHelper.java:202)
I  474.020s run_tests_on_device(008c099374eeb8f3)    	at org.chromium.android_webview.test.AwContentsClientShouldInterceptRequestTest.testBaseUrlOfLoadDataSentInRefererHeader(AwContentsClientShouldInterceptRequestTest.java:827)
I  474.020s run_tests_on_device(008c099374eeb8f3)    	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
I  474.020s run_tests_on_device(008c099374eeb8f3)    	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:555)
I  474.021s run_tests_on_device(008c099374eeb8f3)    	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879)

Most likely the bot's problem.

Sign in to add a comment