I just sent out a PR for Prism, and the java suite executed way too fast: https://github.com/apache/beam/actions/runs/13597430640/attempts/1?pr=34132
And when I looked it said: > Task :runners:prism:java:prismLoopbackValidatesRunnerTests FROM-CACHE which it probably shouldn't be doing for most PRs if we detected it should be running. PR in question: https://github.com/apache/beam/pull/34132 I don't recall seeing this before, though it's probably due to making a refactoring change instead of adding new behavior. Is there a way to convince gradle not to do that? Otherwise changes to Prism won't be properly validated against the Java suite. I thought it was detecting the dependency tree properly, but apparently not. Cheers, Robert
