Yes, it does - you’re awesome, thank you very much! 🙂
connectedCheck failures in cert4android
-
Since the update to use Conscript in 846f0cd3d540677e39491d8ba7e2a34a78b0abfc I get the following connectedCheck failure in cert4android:
> Task :connectedDebugAndroidTest 04:38:23 V/ddms: execute: running am get-config 04:38:23 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1 04:38:23 V/ddms: execute: returning 04:38:23 D/cert4android-debug-androidTest.apk: Uploading cert4android-debug-androidTest.apk onto device 'emulator-5554' 04:38:23 D/Device: Uploading file onto device 'emulator-5554' 04:38:23 D/ddms: Reading file permision of /home/michael/git/cert4android/build/outputs/apk/androidTest/debug/cert4android-debug-androidTest.apk as: rw-r--r-- 04:38:23 V/ddms: execute: running pm install -r -t "/data/local/tmp/cert4android-debug-androidTest.apk" 04:38:23 V/ddms: execute 'pm install -r -t "/data/local/tmp/cert4android-debug-androidTest.apk"' on 'emulator-5554' : EOF hit. Read: -1 04:38:23 V/ddms: execute: returning 04:38:23 V/ddms: execute: running rm "/data/local/tmp/cert4android-debug-androidTest.apk" 04:38:23 V/ddms: execute 'rm "/data/local/tmp/cert4android-debug-androidTest.apk"' on 'emulator-5554' : EOF hit. Read: -1 04:38:23 V/ddms: execute: returning 04:38:23 I/RemoteAndroidTest: Running am instrument -w -r at.bitfire.cert4android.test/androidx.test.runner.AndroidJUnitRunner on Pixel_2_API_28_9.0_(AVD) - 9 04:38:23 V/ddms: execute: running am instrument -w -r at.bitfire.cert4android.test/androidx.test.runner.AndroidJUnitRunner 04:38:25 V/InstrumentationResultParser: INSTRUMENTATION_RESULT: shortMsg=Process crashed. 04:38:25 I/InstrumentationResultParser: test run failed: 'Instrumentation run failed due to 'Process crashed.'' Starting 0 tests on Pixel_2_API_28_9.0_(AVD) - 9 Tests on Pixel_2_API_28_9.0_(AVD) - 9 failed: Instrumentation run failed due to 'Process crashed.' 04:38:25 I/XmlResultReporter: XML test result file generated at /home/michael/git/cert4android/build/outputs/androidTest-results/connected/TEST-Pixel_2_API_28_9.0_(AVD) - 9-cert4android-.xml. Total tests 0, 04:38:25 V/InstrumentationResultParser: INSTRUMENTATION_CODE: 0 04:38:25 V/InstrumentationResultParser: 04:38:25 V/ddms: execute 'am instrument -w -r at.bitfire.cert4android.test/androidx.test.runner.AndroidJUnitRunner' on 'emulator-5554' : EOF hit. Read: -1 04:38:25 V/ddms: execute: returning com.android.builder.testing.ConnectedDevice > No tests found.[Pixel_2_API_28_9.0_(AVD) - 9] FAILED No tests found. This usually means that your test classes are not in the form that your test runner expects (e.g. don't inherit from TestCase or lack @Test annotations). 04:38:25 I/XmlResultReporter: XML test result file generated at /home/michael/git/cert4android/build/outputs/androidTest-results/connected/TEST-Pixel_2_API_28_9.0_(AVD) - 9-cert4android-.xml. Total tests 1, failure 1, 04:38:25 V/ddms: execute: running pm uninstall at.bitfire.cert4android.test 04:38:25 V/ddms: execute 'pm uninstall at.bitfire.cert4android.test' on 'emulator-5554' : EOF hit. Read: -1 04:38:25 V/ddms: execute: returning > Task :connectedDebugAndroidTest FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':connectedDebugAndroidTest'. > There were failing tests. See the report at: file:///home/michael/git/cert4android/build/reports/androidTests/connected/index.html * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.1.1/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 19s 54 actionable tasks: 53 executed, 1 up-to-date -
Has worked here
-
Hm, it’s reliably reproducible here using the Android emulator and testing different Android versions (8.1 and 9.0).
I’ve attached a logcat.txt from a failing test run. logcat.txt
Maybe that helps in finding the cause of the failure.
