The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/fix/gsp-compile-cacheable-8.0.x has failed. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: 7cafb0807babbf0e9a16da446eab40a51f83d37b / Scott Murphy Heiberg <[email protected]> Cache compiled pages again Caching was turned off for compiling pages during the AOT and native-image work, while pages compiled by Groovy 6 were failing under Groovy 5. Groovy 6 compiles property writes to invokedynamic call sites (GROOVY-12138), which Groovy 5 cannot link, and the page compiler always compiles with indy on. Turning the cache off made sure no build could be handed pages compiled by a different Groovy. The key already keeps those builds apart. AbstractCompile declares the classpath a @Classpath input, so the Groovy the forked compiler runs from is fingerprinted by content, and the launcher's language version and the target compatibility say which Java. With caching turned on, -Dorg.gradle.caching.debug=true lists them: Appending input value fingerprint for 'javaLauncher.metadata.languageVersion' Appending input value fingerprint for 'targetCompatibility' Appending input file fingerprints for 'classpath' ... - CLASSPATH{...} Uncached, every fresh checkout, worktree and CI run forks a compiler for each project with views, even when nothing it reads has changed. The tests restore pages compiled in one checkout into a copy in another directory, and compile them again when the classpath carries another Groovy or the build asks for another Java. Report URL: https://github.com/apache/grails-core/actions/runs/39535196369 With regards, GitHub Actions via GitBox
