Changing instrumented test target causes configuration cache miss [373074302]

Assigned

Bug

Status Update

No update yet.

Description

ni...@hinge.co

created issue #1

Oct 13, 2024 11:45AM

When you run an instrumented test it will cause a configuration cache miss if yotestu change the test target from the previous run:

Run an instrumentation test by running a specific test class
When it's complete try running another test class

I'd expect Gradle to be able to reuse the configuration cache from the previous run but what happens instead is a cache miss the following message:

Calculating task graph as configuration cache cannot be reused because the set of Gradle properties has changed: 'android.testInstrumentationRunnerArguments.class' was removed.

Studio Build: Android Studio Koala Feature Drop | 2024.1.2 Patch 1
Version of Gradle Plugin: 8.6.1
Version of Gradle: 8.10
Version of Java: 23
OS: macOS 14.7

Comments

jo...@google.com <jo...@google.com> Oct 15, 2024 02:32PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> #2Oct 16, 2024 06:27PM

Reassigned to je...@google.com.

Disregard - after adding

enableUnitTestCoverage = false
enableAndroidTestCoverage false

Thinks started to work again.

But for what it is worth - the error message could have been more helpful.

Message last modified on Oct 16, 2024 06:32PM

ni...@hinge.co <ni...@hinge.co> #3Oct 17, 2024 05:14PM

Well the error message is that it tried to configure jacoco task and failed, so it works for you because you disabled the feature.

So the error message is indicative of a bigger problem. Oviously, 8.2 is pretty old for us, not sure you are interested in trying 8.8.

The easiest would be to have a project reproducing the issue, if that's possible, we'll look into it.

je...@google.com <je...@google.com> #4Oct 17, 2024 05:25PM

We tried bumping things up to 8.8 but that causes other problems that we need to resolve first. There was a long list of issues with name spaces and what not due to clashes across different 3rd part integrations that we have in the app.
Unfortunately we haven't had the resources to keep things up to date for a long time - and now every possible problem is just piling up...

I'll get back once we manage to upgrade to 8.8...

ni...@hinge.co <ni...@hinge.co> #5Oct 18, 2024 02:45PM

Normally deferring reading these until task execution is preferred, what is the use of that property?

System properties or files won't help, reading those during configuration will also cause a miss.

mi...@gmail.com <mi...@gmail.com> #6Dec 4, 2024 07:26PM

I'd also love to see this fixed.

Noting that the code was changed specifically to set a configuration-time dependency on these parameters in

https://cs.android.com/android-studio/platform/tools/base/+/73e53320032cbe1a2f540014aeda9e50bbe26a00 . I don't know why really, the bug

https://issuetracker.google.com/issues/155766476 that the work was done under is much more generic (and indeed some other gradle parameters can conceivably affect the configuration phase).

je...@google.com <je...@google.com> #7Feb 3, 2025 03:52PM

we are revamping a lot of the testing infrastructure code so this will need to be fixed as part of this effort.