From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

&gt; Normally `maxHeapSize` should not be an input for test tasks.
Could you guide me on how to make the above statement true?

In our setup, we have such a snippet that sets `maxHeapSize`.
```tasks.withType(Test) {
  maxHeapSize = rootProject.findProperty("testMaxHeapSize") ?: '1024m'
}```
If I run `gradle test` and then `gradle clean test -PtestMaxHeapSize=2048m` it reruns the tests instead of taking the entry from cache.

Here's a screenshot from build scan comparison:

Unfortunately, I'm back at this problem again. I can see a situation where there are two CI builds, let's say A and B. B starts only after A has finished. They are both executed on the exact same checkout. The difference is the machines they run on and, thus, the memory settings, etc. Now when I compare the build scans from these two builds I can see that B didn't take test results from the cache. The only difference that GE indicates is this: `Input 'jvmArgumentProviders.$0' is in both builds but the values are different.`. I'm not exactly sure what this refers to and I don't seem to be able to reproduce it locally by providing different values through the jvmArgumentsProvider I add either.

Do you know what might be going on here by any chance?