The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/feat/gorm-registry-consolidated has failed. Run started by GitHub user borinquenkid (triggered by borinquenkid).
Head commit for run: 9e3e06ddf4020e60def59d9b5f799c4d94c3571f / Walter Duque de Estrada <[email protected]> Remove GORM maxParallelForks=1 isolation, restore standard test parallelism jdaugherty asked why GORM-dependent test modules needed isolation from maxParallelForks given each Gradle fork is an independent JVM. Verified empirically that no conflict exists: a full CI run with the isolation removed (configuredTestParallel forks for grails-datamapping-core and every dependent module, run concurrently on the same shared macos-latest runner used elsewhere in this PR's CI) passed cleanly, including GormRegistryConcurrencySpec. GormRegistry is a per-JVM singleton, and each forked JVM has its own independent instance with no shared memory across forks, so there was never a cross-fork data hazard to isolate against. Reference run: https://github.com/apache/grails-core/actions/runs/32087151762 Co-Authored-By: Claude Sonnet 5 <[email protected]> Report URL: https://github.com/apache/grails-core/actions/runs/32138320105 With regards, GitHub Actions via GitBox
