New issue
Advanced search Search tips

Issue 627142 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

unit_tests fail on pre-L Android

Project Member Reported by wychen@chromium.org, Jul 11 2016

Issue description

unit_tests fail on Android

https://uberchromegw.corp.google.com/i/chromium.android/builders/Jelly%20Bean%20Tester/builds/5130
https://uberchromegw.corp.google.com/i/chromium.android/builders/KitKat%20Tablet%20Tester/builds/4777
https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/35237

The error message is:

I  106.476s TimeoutThread-1-for-delete_temporary_file(0cba90a3032fdbe3)  [host]> /b/build/slave/Android_Tests__dbg_/build/src/third_party/android_tools/sdk/platform-tools/adb -s 0cba90a3032fdbe3 shell 'rm -f /data/local/tmp/temp_file-4e03d3d5131eb'
I  106.479s list_tests(0cba90a3032fdbe3)  No tests found. Output:
I  106.479s list_tests(0cba90a3032fdbe3)    INSTRUMENTATION_RESULT: shortMsg=java.lang.AssertionError
I  106.479s list_tests(0cba90a3032fdbe3)    INSTRUMENTATION_RESULT: longMsg=java.lang.AssertionError
I  106.480s list_tests(0cba90a3032fdbe3)    INSTRUMENTATION_CODE: 0
 

Comment 1 by wychen@chromium.org, Jul 11 2016

It works fine on "Android Tests", but failed on "Android Tests (dbg)".

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests/builds/28830

"Android Tests" is on swarming, but "Android Tests (dbg)" is not. Not sure if this causes any differences.

Comment 2 by wychen@chromium.org, Jul 11 2016

 Issue 627107  has been merged into this issue.

Comment 4 by wychen@chromium.org, Jul 11 2016

Looks like the Java Assertion happened when running this command:

p=org.chromium.native_test;am instrument -w -e "$p".NativeTestInstrumentationTestRunner.ShardNanoTimeout 30000000000 -e "$p".NativeTestInstrumentationTestRunner.NativeTestActivity "$p".NativeUnitTestActivity -e "$p".NativeTest.CommandLineFlags --gtest_list_tests "$p"/"$p".NativeTestInstrumentationTestRunner

Comment 5 by wychen@chromium.org, Jul 11 2016

Tried to run the pre-built files from gs://chromium-linux-archive/chromium.linux/Android Builder (dbg)/full-build-linux_f6a90668df362525557e37bef4cf4a079f9d8aad.zip (URL from https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/35237/steps/extract%20build/logs/stdio), but still couldn't repro.
#5: What OS version were you trying to repro on? asserts don't do anything on L+

Comment 7 by wychen@chromium.org, Jul 12 2016

#6: This must be the reason. I'm using M.

I'm using trybot to see if reverting https://codereview.chromium.org/1486053003/ fixes it.
also, from the logcat:

0210f:  07-11 14:29:43.369  4351  4351 D AndroidRuntime: Shutting down VM
0210f:  07-11 14:29:43.369  4351  4351 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x41585ba8)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime: FATAL EXCEPTION: main
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime: Process: org.chromium.native_test, PID: 4351
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime: java.lang.AssertionError
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at org.chromium.base.CommandLine.getInstance(CommandLine.java:118)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at org.chromium.base.EarlyTraceEvent.maybeEnable(EarlyTraceEvent.java:86)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at org.chromium.base.TraceEvent.maybeEnableEarlyTracing(TraceEvent.java:196)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at org.chromium.chrome.browser.ChromeApplication.onCreate(ChromeApplication.java:210)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4328)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.app.ActivityThread.access$1500(ActivityThread.java:135)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.os.Handler.dispatchMessage(Handler.java:102)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.os.Looper.loop(Looper.java:136)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at android.app.ActivityThread.main(ActivityThread.java:5001)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at java.lang.reflect.Method.invokeNative(Native Method)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at java.lang.reflect.Method.invoke(Method.java:515)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
0210f:  07-11 14:29:43.369  4351  4351 E AndroidRuntime:  at dalvik.system.NativeStart.main(Native Method)
0210f:  07-11 14:29:43.369   778   790 W ActivityManager: Error in app org.chromium.native_test running instrumentation ComponentInfo{org.chromium.native_test/org.chromium.native_test.NativeTestInstrumentationTestRunner}:
0210f:  07-11 14:29:43.369   778   790 W ActivityManager:   java.lang.AssertionError
0210f:  07-11 14:29:43.369   778   790 W ActivityManager:   java.lang.AssertionError
#7: that certainly appears to be the culprit, given the EarlyTraceEvent appearance in the logcat exception trace.
Summary: unit_tests fail on pre-L Android (was: unit_tests fail on Android)
Status: Fixed (was: Unconfirmed)

Sign in to add a comment