mannodermaus
commented
1 month ago Thanks for reporting – what an esoteric stack trace! I will try to reproduce this myself, but please allow me a few follow-up questions first:
- What's the version of AGP you are using in this project?
- To clarify, you are referring to parallel instrumentation tests, right? I can see some UTP references in the trace and thus assume that this is running on an actual device?
- Assuming it's an instrumentation test, could you share the snippet from your build script where parallelization is enabled?
- Could you share a little info about the particular test that is failing? If it's not possible to copy the entire class, then feel free to redact the body of the method itself and only let me know what the test does on a high level (i.e. is it using Espresso, Compose, are there any resource locks, etc)
I do know that there is apparently some fixes related to parallel testing in JUnit 5.11.2, so I wonder if there is an unexpected side effect for the Android environment introduced by those. If you want, you could also try the intermittent plugin version 1.11.1.0, which also ships with instrumentation 1.6.0. Maybe if that also works, we have narrowed down the problem surface. Thanks in advance!
mgroth0
Everything works as expected using versions 1.11.0 and 1.5.0.
Then after upgrading to 1.11.2 and 1.6.0, @ParameterizedTest causes an exception to be thrown from some internal context. This exception is very difficult to see as it doesn't show up for me in the test report or the regular build output. I only see it with debug output. The build says one of my parameterized tests failed, which is misleading since the exception came from some internal issue in the test framework.
I want to also say I don't really understand what's going on here, so if the issue isn't clear please let me know what further information I can provide. Creating a reproducer might take a while, but I can try that as a last resort.
For now, downgrading back to 1.11.0 and 1.5.0 prevented the issue from happening.