The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/feat/add-configuration-cache-support has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: b1fef67eb477a7380740c66adea00e78cd234036 / James Daugherty <[email protected]> Address review feedback on the configuration cache support - The Forge asciidoctor template names the task instead of its type, which the applied script cannot see; a test-core spec builds a generated app's guide. - publishAllToMavenLocal reads the project directory while it is configured and logs through the task. - The vulnerability scan's built-in exclusions are the property's value, so exclude(...) adds to them. A scan whose lookup fails writes an error report, and the summary lists it instead of reporting a clean build. An OSV answer with fewer results than queries fails instead of caching the rest as clean, and a request still throttled after the retries reports its last status. Waiting to retry stops when the build is cancelled. - springBoot.mainClass and mainClassName read the main class through a value source, which the configuration cache obtains again on reuse, instead of a project.provider evaluated when the entry is stored. - ConvertAsciidocTask declares the files the documents include and keeps path attributes out of its inputs, so changed examples reconvert the guides and the build cache works across machines; TestKit specs cover the task and FetchTagsTask, which is now untracked so new tags are never missed. - A CI job runs the build-logic tests. - The configuration cache note moves to a new "Upgrading from Grails 8.0 to Grails 8.1" page, which says it needs the 8.1 Gradle plugins and BOM. Report URL: https://github.com/apache/grails-core/actions/runs/37398076233 With regards, GitHub Actions via GitBox
