The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/perf/request-path-8.0.x has failed. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: 14ae491d5956f6ff04897e1b25820fb55fd9b090 / Scott Murphy Heiberg <[email protected]> build: move the benchmark harness under grails-test-examples Review asked for one of two things: the module under grails-test-examples, or an exclusion in the root build. The exclusion went in first and was the wrong choice. Every project in the repository carries a prefix that says what it is - four grails-test-suite, sixty-seven grails-test-examples, one grails-doc, and the framework modules. This one was declared in the framework include block between grails-bootstrap and grails-beans-dsl while being unpublishable and existing only to exercise the framework, so three mechanisms that read the prefix - the test project list, the cli auto-provision default, the doc and cli classification - each had to be told about it separately. Its own build file already listed four plugins it omits for the same reason. Naming it in testProjectsStartWith would have made that five, and left the next mechanism to find out the hard way. The prefix now carries the classification, so the exclusion is reverted with it. Renaming costs five files: the settings and root build, the benchmark workflow's task paths, the RAT exclusion for the golden report fixtures, and the module's own README. The workflow also probes the base revision for the project directory before comparing against it; that path will not exist on a base from before this commit, which the workflow already handles by falling back to head-only mode. Report URL: https://github.com/apache/grails-core/actions/runs/33660504287 With regards, GitHub Actions via GitBox
