New issue
Advanced search Search tips

Issue 646843 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

org.chromium.content.browser.JavaBridgeChildFrameTest#testHolderFrame flaky

Project Member Reported by grt@chromium.org, Sep 14 2016

Issue description

For example, from https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/31942/steps/content_shell_test_apk%20on%20Android/logs/stdio:

I  112.478s run_tests_on_device(03d648c009d3a730)  detected failure in org.chromium.content.browser.JavaBridgeChildFrameTest#testHolderFrame. raw output:
I  112.478s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: numtests=1
I  112.478s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: stream=
I  112.478s run_tests_on_device(03d648c009d3a730)    org.chromium.content.browser.JavaBridgeChildFrameTest:
I  112.478s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: id=InstrumentationTestRunner
I  112.478s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: test=testHolderFrame
I  112.478s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: class=org.chromium.content.browser.JavaBridgeChildFrameTest
I  112.479s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: current=1
I  112.479s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS_CODE: 1
I  112.479s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: numtests=1
I  112.479s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: stream=
I  112.479s run_tests_on_device(03d648c009d3a730)    Error in testHolderFrame:
I  112.479s run_tests_on_device(03d648c009d3a730)    java.util.concurrent.TimeoutException
I  112.479s run_tests_on_device(03d648c009d3a730)    	at org.chromium.content.browser.JavaBridgeChildFrameTest$2Test.waitForInjection(JavaBridgeChildFrameTest.java:193)
I  112.479s run_tests_on_device(03d648c009d3a730)    	at org.chromium.content.browser.JavaBridgeChildFrameTest.testHolderFrame(JavaBridgeChildFrameTest.java:216)
I  112.479s run_tests_on_device(03d648c009d3a730)    	at java.lang.reflect.Method.invokeNative(Native Method)
I  112.479s run_tests_on_device(03d648c009d3a730)    	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at org.chromium.content_shell_apk.ContentShellTestBase.runTest(ContentShellTestBase.java:233)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
I  112.480s run_tests_on_device(03d648c009d3a730)    	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)
I  112.480s run_tests_on_device(03d648c009d3a730)    
I  112.480s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: id=InstrumentationTestRunner
I  112.480s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: test=testHolderFrame
I  112.480s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: class=org.chromium.content.browser.JavaBridgeChildFrameTest
I  112.480s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: stack=java.util.concurrent.TimeoutException
I  112.480s run_tests_on_device(03d648c009d3a730)    	at org.chromium.content.browser.JavaBridgeChildFrameTest$2Test.waitForInjection(JavaBridgeChildFrameTest.java:193)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at org.chromium.content.browser.JavaBridgeChildFrameTest.testHolderFrame(JavaBridgeChildFrameTest.java:216)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at java.lang.reflect.Method.invokeNative(Native Method)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at org.chromium.content_shell_apk.ContentShellTestBase.runTest(ContentShellTestBase.java:233)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
I  112.481s run_tests_on_device(03d648c009d3a730)    	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)
I  112.481s run_tests_on_device(03d648c009d3a730)    
I  112.481s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS: current=1
I  112.481s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_STATUS_CODE: -1
I  112.481s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_RESULT: stream=
I  112.481s run_tests_on_device(03d648c009d3a730)    Test results for BaseChromiumInstrumentationTestRunner=.E
I  112.482s run_tests_on_device(03d648c009d3a730)    Time: 5.982
I  112.482s run_tests_on_device(03d648c009d3a730)    
I  112.482s run_tests_on_device(03d648c009d3a730)    FAILURES!!!
I  112.482s run_tests_on_device(03d648c009d3a730)    Tests run: 1,  Failures: 0,  Errors: 1
I  112.482s run_tests_on_device(03d648c009d3a730)    
I  112.482s run_tests_on_device(03d648c009d3a730)    
I  112.482s run_tests_on_device(03d648c009d3a730)    INSTRUMENTATION_CODE: -1
 

Comment 1 by boliu@chromium.org, Sep 14 2016

Owner: ----
Status: Available (was: Assigned)
mnaganov no longer works on chromium

And yes, that test made my list of flaky tests as well (I got the data from flakiness dashboard rather than actual red bots)
Cc: michaelbai@chromium.org
Michael owns the javabridge stuff now?

Comment 3 by sgu...@chromium.org, Sep 17 2016

Cc: -michaelbai@chromium.org
Owner: michaelbai@chromium.org
let's make this official
Status: Assigned (was: Available)
Looks like this was already assigned to Michael, but I'm changing this from "available" to "assigned" to get this officially out of the queue.

Comment 5 by battre@chromium.org, Nov 29 2016

 Issue 669350  has been merged into this issue.
Project Member

Comment 6 by chromium...@appspot.gserviceaccount.com, Nov 30 2016

Labels: Sheriff-Chromium
Detected 10 new flakes for test/step "org.chromium.content.browser.JavaBridgeChildFrameTest#testHolderFrame". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUAsSBUZsYWtlIkVvcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLkphdmFCcmlkZ2VDaGlsZEZyYW1lVGVzdCN0ZXN0SG9sZGVyRnJhbWUM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 7 by battre@chromium.org, Nov 30 2016

Labels: -Pri-2 -Sheriff-Chromium Pri-1
Increasing priority and taking this out of the sheriff queue again.
Project Member

Comment 8 by chromium...@appspot.gserviceaccount.com, Dec 1 2016

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "org.chromium.content.browser.JavaBridgeChildFrameTest#testHolderFrame". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUAsSBUZsYWtlIkVvcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLkphdmFCcmlkZ2VDaGlsZEZyYW1lVGVzdCN0ZXN0SG9sZGVyRnJhbWUM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).
Labels: -Sheriff-Chromium
Removing sheriff label as this has an assignee. Please look into this as it slows down these trybots for other users.

It seems to be timing out in waitForInjection, but it's not obvious to me whether this timeout is too small, or there is some deeper issue.
Project Member

Comment 10 by bugdroid1@chromium.org, Dec 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0861de9d8dbff14658f3da8375b4526b345c4203

commit 0861de9d8dbff14658f3da8375b4526b345c4203
Author: grt <grt@chromium.org>
Date: Mon Dec 12 10:53:26 2016

Disable flaky org.chromium.content.browser.JavaBridgeChildFrameTest#testHolderFrame.

This test is flaky on chromium.linux Android Tests and Android Tests (dbg).

BUG=646843
TBR=michaelbai@chromium.org

Review-Url: https://codereview.chromium.org/2568073002
Cr-Commit-Position: refs/heads/master@{#437845}

[modify] https://crrev.com/0861de9d8dbff14658f3da8375b4526b345c4203/content/public/android/javatests/src/org/chromium/content/browser/JavaBridgeChildFrameTest.java

Sign in to add a comment