borinquenkid commented on PR #16066: URL: https://github.com/apache/grails-core/pull/16066#issuecomment-5328315747
On the parallelism restriction you asked about: fair ask, and it exposed that the restriction wasn't earning its keep. `GormRegistry` is a per-JVM singleton by design — it models exactly one running application instance, same as production, where you'd never run multiple redundant forks of the same app sharing a registry. That's real design intent, but it doesn't imply Gradle's test forks need isolating from each other: each fork already gets its own independent registry instance with zero shared state. The `maxParallelForks=1` gate for GORM-dependent modules was a proactive safeguard added without an observed failure behind it. Tested that assumption directly: ran a full CI pass with the isolation removed (`configuredTestParallel` forks for `grails-datamapping-core` and every dependent module, running concurrently on the same shared `macos-latest` runner) — it passed clean, including `GormRegistryConcurrencySpec` under real concurrent-fork load. Removed the whole `isGormProject`/`dependsOnProject` mechanism in 9e3e06ddf4; tests now run at full parallelism like everything else. Run: https://github.com/apache/grails-core/actions/runs/32087151762 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
