During benchmark validation, the action-overhead v4.9.1-vs-main run showed that the candidate arm could not restore the cache entry seeded by v4.9.1 on the same fixture. v4.9.1 seeded setup-java-macOS-x64-maven-597605af...; main computed a different key for the same benchmark tree and reported maven cache is not found in the maven-hit profile. This means pairwise restore benchmarks cannot compare main to v4.9.1 on a shared cache entry without confounding the result with a cache miss. This issue tracks the benchmark limitation, not an upstream setup-java fix request.
During benchmark validation, the
action-overheadv4.9.1-vs-main run showed that the candidate arm could not restore the cache entry seeded by v4.9.1 on the same fixture. v4.9.1 seededsetup-java-macOS-x64-maven-597605af...;maincomputed a different key for the same benchmark tree and reportedmaven cache is not foundin themaven-hitprofile. This means pairwise restore benchmarks cannot comparemainto v4.9.1 on a shared cache entry without confounding the result with a cache miss. This issue tracks the benchmark limitation, not an upstream setup-java fix request.