New issue
Advanced search Search tips

Issue 765714 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

[Android] Cannot lists tests for chrome_public_test_apk when listing tests compiled for release

Project Member Reported by pkotw...@chromium.org, Sep 15 2017

Issue description

I   13.736s Main  Could not get tests from pickle: /usr/local/google/home/pkotwicz/clankium3/src/out/gn_Release/apks/ChromePublicTest.apk-runner.pickle does not exist.
1359 I   13.736s Main  Getting tests by having org.chromium.base.test.BaseChromiumAndroidJUnitRunner list them.
1360 D   13.738s TimeoutThread-1-for-list_tests(HT4ABJT05147)  Large output mode enabled. Will write output to device and read results from file.
1361 I   13.739s TimeoutThread-1-for-list_tests(HT4ABJT05147)  [host]> /usr/local/google/home/pkotwicz/clankium3/src/third_party/android_tools/sdk/platform-tools/adb -s HT4ABJT05147 shell '( ( p=org.chromium.chrome.tests;am instrument -w -e log tru     e -e org.chromium.base.test.BaseChromiumAndroidJUnitRunner.TestList /storage/emulated/legacy/temp_file-a09f0aa0b1eb1.json "$p"/org.chromium.base.test.BaseChromiumAndroidJUnitRunner )>/data/local/tmp/temp_file-f65a609659ee3 2>&1 );echo %$?'
1362 D   21.415s TimeoutThread-1-for-list_tests(HT4ABJT05147)  STDOUT+STDERR: %0
1363 I   21.416s TimeoutThread-1-for-list_tests(HT4ABJT05147)  [host]> /usr/local/google/home/pkotwicz/clankium3/src/third_party/android_tools/sdk/platform-tools/adb -s HT4ABJT05147 pull /data/local/tmp/temp_file-f65a609659ee3 /tmp/tmpajqxRT/tmp_ReadFileWithPull
1364 D   21.496s TimeoutThread-1-for-list_tests(HT4ABJT05147)  STDOUT+STDERR: [100%] /data/local/tmp/temp_file-f65a609659ee3
1365 /data/local/tmp/temp_file-f65a609659ee3: 1 file pulled. 0.0 MB/s (208 bytes in 0.041s)
1366 I   21.498s TimeoutThread-1-for-delete_temporary_file(HT4ABJT05147)  [host]> /usr/local/google/home/pkotwicz/clankium3/src/third_party/android_tools/sdk/platform-tools/adb -s HT4ABJT05147 shell 'rm -f /data/local/tmp/temp_file-f65a609659ee3'


1367 E   21.515s list_tests(HT4ABJT05147)  Unexpected output while listing tests:
1368 E   21.515s list_tests(HT4ABJT05147)    INSTRUMENTATION_RESULT: shortMsg=java.lang.NoClassDefFoundError
1369 E   21.516s list_tests(HT4ABJT05147)    INSTRUMENTATION_RESULT: longMsg=java.lang.NoClassDefFoundError: org.chromium.content.browser.FloatingActionModeCallback
1370 E   21.516s list_tests(HT4ABJT05147)    INSTRUMENTATION_CODE: 0



I   21.518s TimeoutThread-1-for-list_tests(HT4ABJT05147)  [host]> /usr/local/google/home/pkotwicz/clankium3/src/third_party/android_tools/sdk/platform-tools/adb -s HT4ABJT05147 pull /storage/emulated/legacy/temp_file-a09f0aa0b1eb1.json /tmp/tmpXeFEUk/list_tests.json
1372 D   21.554s TimeoutThread-1-for-list_tests(HT4ABJT05147)  STDOUT+STDERR: adb: error: remote object '/storage/emulated/legacy/temp_file-a09f0aa0b1eb1.json' does not exist
1373 D   21.580s TimeoutThread-1-for-delete_temporary_file(HT4ABJT05147)  STDOUT+STDERR: 
1374 C   21.582s list_tests(HT4ABJT05147)  (TimeoutThread-1-for-list_tests(HT4ABJT05147)) Exception on PullFile(HT4ABJT05147, /storage/emulated/legacy/temp_file-a09f0aa0b1eb1.json, /tmp/tmpXeFEUk/list_tests.json, retries=2, timeout=30), attempt 1 of 3: AdbCommandFailedError("(device: HT4ABJT05147) adb pull /storage/emulated/legacy/temp_file-a09f0aa0b1eb1.json /tmp/tmpXeFEUk/list_tests.json: failed with exit status 1 and output:\n- adb: error: remote object '/storage/emulated/legacy/temp_file-a09f0aa0b1eb1.json' does not exist\n",)
 
Labels: OS-Android
The tests run fine when compiled with is_debug=true

For the sake of completeness I ran the tests via:
out/gn_Release/bin/run_chrome_public_test_apk -v -v -f *Webapp*
GN args:
is_debug=false
is_component_build=true
use_goma=true
target_os="android"
is_clang=true


Owner: agrieve@chromium.org
Status: Started (was: Untriaged)
Repro's for me as well. And I saw the same thing last week (and it went away in the interim!)
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 16 2017

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

commit fc9e7a90fdeb4371bfc97e13a8d1db5217697576
Author: Andrew Grieve <agrieve@chromium.org>
Date: Sat Sep 16 02:35:12 2017

Android: Update test proguard rules to keep more things

And also add a special case to ReTrace regex to deobfuscate a junit
message.

Bug:  765714 
Change-Id: I2ba53b00a563f67eef7eb1910b2f894746abfb3a
Reviewed-on: https://chromium-review.googlesource.com/669011
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#502476}
[modify] https://crrev.com/fc9e7a90fdeb4371bfc97e13a8d1db5217697576/build/android/stacktrace/java/org/chromium/build/FlushingReTrace.java
[modify] https://crrev.com/fc9e7a90fdeb4371bfc97e13a8d1db5217697576/build/android/stacktrace/java_deobfuscate_test.py
[modify] https://crrev.com/fc9e7a90fdeb4371bfc97e13a8d1db5217697576/testing/android/proguard_for_test.flags

Status: Fixed (was: Started)

Sign in to add a comment