New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 717267 link

Starred by 1 user
Status: Fixed
Owner:
█ aelias@chromium.org
inactive
Closed: May 2017
Cc:
agrieve@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

testRedirectCustomTabActivityToFirstRun failing with NoClassDefFoundError: android.support.v4.content.ContextCompatJellybean

Project Member Reported by aelias@chromium.org, May 1 2017 
https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20%28dbg%29
First failure: https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/42159


C 1341.406s Main  [FAIL] org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest#testRedirectCustomTabActivityToFirstRun:
C 1341.406s Main  java.lang.NoClassDefFoundError: android.support.v4.content.ContextCompatJellybean
C 1341.406s Main  	at android.support.v4.content.ContextCompat.startActivity(ContextCompat.java:151)
C 1341.406s Main  	at android.support.customtabs.CustomTabsIntent.launchUrl(CustomTabsIntent.java:262)
C 1341.406s Main  	at org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest$2.run(FirstRunIntegrationTest.java:76)
C 1341.406s Main  	at org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest.runFirstRunRedirectTestForActivity(FirstRunIntegrationTest.java:125)
C 1341.406s Main  	at org.chromium.chrome.browser.firstrun.FirstRunIntegrationTest.testRedirectCustomTabActivityToFirstRun(FirstRunIntegrationTest.java:69)
C 1341.406s Main  	at java.lang.reflect.Method.invokeNative(Native Method)
C 1341.406s Main  	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
C 1341.406s Main  	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
C 1341.406s Main  	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
C 1341.406s Main  	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
C 1341.406s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
C 1341.406s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
C 1341.406s Main  	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
C 1341.406s Main  	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

Comment 1 by aelias@chromium.org, May 1 2017 

The only suspicious change in the range is https://codereview.chromium.org/2854503002 "[Android] Keep extracted secondary dex files when clearing data in tests."  I don't have a specific theory why but it does seem from  http://crbug.com/716143  that multidex can be prone to class-not-found problems.  jbudorick@: is the theory plausible enough to revert?

Comment 2 by jbudorick@chromium.org, May 1 2017 

Yeah, seems plausible, especially since I added some usage of ContextCompat in that CL. I'm surprised that it consistently fails on exactly one test, though. I'll have to dig into that.

Revert's in the CQ.

Comment 3 by jbudorick@chromium.org, May 2 2017

Status: Fixed (was: Assigned)
Revert appears to have worked.
►

Sign in to add a comment