-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test execution hangs with invalid classpath (1.5.0 vs fragment-testing) #1589
Comments
Thanks for the report. I can repro on your project, but attempting to replicate the same scenario on https://github.com/android/testing-samples/tree/main/ui/espresso/FragmentScenarioSample always immediately fails with a build error. Sorry I'm not very experienced with gradle and am not able to follow your project's setup to see what the differences are. |
Same experience on my private project, +1. I believe any instrumentation test (not just If it was failing instantly with a meaningful error message, maybe it had to do with some sort of caching issue, but I'm also no gradle expert... just an early updater :P |
@yuuki3655 any ideas? |
"androidx.test.platform.io.PlatformTestStorageRegistry" is part of androidx.test:monitor:1.6.0 |
@TWiStErRob would you mind filing this against gradle instead? https://developer.android.com/studio/report-bugs. There is not much we can do on the androidx.test.runner side to handle a low level class missing exception this early in the run, and filing against gradle will ensure we can get the experts to look at it. I'm of the opinion there are two bugs here:
|
@QArtur99 comment brought me to the right path although I didn't have to add the
So I needed to add the following tomy proguard rules:
|
Description
I just experienced this too, with the standard setup updating all libs at once. Excluding core helped. The reason I'm opening an issue is because my behavior is not the same as #1585, and I think the developer experience could be better. The key here is that the execution hangs, Gradle never fails. What would be expected is a real failure because there's something fundamentally wrong with the tests.
Steps to Reproduce
gradlew :feature:base:connectedDebugAndroidTest
with an emulator or device.Expected Results
Failure. At least something like:

Actual Results
Exception in logcat:
and
:feature:base:connectedDebugAndroidTest
doesn't ever complete.Full logcat
AndroidX Test and Android OS Versions
androidx-test = "1.5.0"
androidx-test-espresso = "3.5.0"
Emulator API 31, 29
Link to a public git repo demonstrating the problem:
See repro above.
The text was updated successfully, but these errors were encountered: