The cache suite isolates STIM_BUILD_CACHE/STIM_METRO_CACHE to throwaway roots so every number is a real before/after around a cold compile, but GRADLE_USER_HOME is the one cache root it does not isolate. A machine cache already holding the fixture's task outputs forces the gradle-cache check into its warm mode (engagement proven by loads, storing not exercised — see #134). Pointing wt1 at a throwaway GRADLE_USER_HOME would make storing always measurable, at the cost of a truly uncached (slower) Gradle build. Raised by the #134 review.
The cache suite isolates STIM_BUILD_CACHE/STIM_METRO_CACHE to throwaway roots so every number is a real before/after around a cold compile, but GRADLE_USER_HOME is the one cache root it does not isolate. A machine cache already holding the fixture's task outputs forces the gradle-cache check into its warm mode (engagement proven by loads, storing not exercised — see #134). Pointing wt1 at a throwaway GRADLE_USER_HOME would make storing always measurable, at the cost of a truly uncached (slower) Gradle build. Raised by the #134 review.