jamesfredley opened a new pull request, #16534: URL: https://github.com/apache/grails-core/pull/16534
## Summary Merging `8.1.x` into `9.0.x` (`c3b2ea8`) left CI, Coverage, and the Groovy Snapshot Canary red on both `9.0.x` and `9.1.x` (those tips are the same commit). The other workflows on that commit are green. The three red CI jobs are the Hibernate 7 shards whose task list includes `:grails-data-hibernate7-core:test`: - Hibernate7 Functional Tests (Java 25, indy=false) - Hibernate7 Functional Tests (Java 21, indy=true) - Hibernate7 Functional Tests (Java 21, indy=false, shard 2) Each one dies with `java.lang.OutOfMemoryError: Java heap space` in that task, after the worker has already been running for a long time. Coverage (`:grails-data-hibernate7-core:test FAILED`) and Groovy Snapshot Canary shard 2 fail in the same task the same way. `gradle/hibernate7-test-config.gradle` does not apply the shared test config, so `forkEvery` stayed 0 and one JVM executed every class assigned to the task. The specs that came over with `8.1.x` push that long-lived worker over its heap. This is not a new assertion failure. ## Change Recycle Hibernate 7 test workers on the same cadence as the other unit tests: `forkEvery` 50 on CI and 100 locally, still overridable with `-PforkEveryUnitTest`. Cap that single worker at 2g. `maxParallelForks` stays at its default of 1, so the worker no longer takes the ergonomic heap (larger than 2g on the 16 GB Linux runners) for the whole task. `9.1.x` is the same commit as `9.0.x`, so it stays red until this change is merged forward. ## Test plan - [x] `:grails-data-hibernate7-core:test` completed locally with `CI=true` under these fork and heap settings - [ ] Hibernate7 Functional Tests on this PR, including the three shards that failed on `c3b2ea8` - [ ] Coverage and the Groovy Snapshot Canary on this PR -- 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]
