The GitHub Actions job "SiteMesh 2 Compatibility" on grails-core.git/revert/16192-async-changes has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: d9d9d64e0ab089f4dbf6ef4c5d51bc27a188bce7 / James Daugherty <[email protected]> Run the isolated tests in the web suite Same defect as the uber suite, and the same fifty tests' worth of consequence. execIsolatedTests is registered rather than being the task the java plugin creates, so it had neither testClassesDirs nor classpath and was NO-SOURCE: success, having run nothing. `test` excludes those same classes, so they ran nowhere. There is a third reason here, on top of the two the uber suite had. Nothing declared this task as work: `build` runs `check`, `check` ran `test`, and execIsolatedTests was reachable only by naming it. The shard plugin collects it through tasks.withType(Test), which is why the joint workflow reached it at all and gradle.yml never did. `check` now depends on it. All fifty pass. JSONBindingTests and AutoParams*MarshallingTests are dropped from the list. 1e38f1b5ea deleted all three of those classes in June 2013 and added nothing: the feature went, so the tests went with it, and naming them here selects nothing and excludes nothing. Every other entry that matches no class in this project is left alone, because those tests were moved rather than deleted -- GSPResponseWriterSpec and pages/ext/jsp to grails-gsp, GroovyPageAttributesTests to grails-taglib -- and whether their successors still need isolating is a question about those projects, not this list. Report URL: https://github.com/apache/grails-core/actions/runs/32866498436 With regards, GitHub Actions via GitBox
