The GitHub Actions job "CI" on grails-core.git/feat/sql-tail-command has succeeded. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 428ae475badd5fd12b40aac502bc7b598b1a10a5 / James Daugherty <[email protected]> Let the MongoDB modules' test compile use the shared compiler heap The shared MongoDB test scripts set `groovyOptions.forkOptions.jvmArgs = ['-Xmx768m']` on `compileTestGroovy`. Gradle builds the Groovy compiler daemon's command line from the javac-side `options.forkOptions.jvmArgs`, where `CompilePlugin` puts `-Xmx2G` for every module, followed by the groovy-side list, and the last `-Xmx` wins: the MongoDB modules' test compile forks ran with a 768 MB heap while every other module got 2 GB. The cap came over from the standalone gorm-mongodb build in a58aa145cf, where it sized the only compiler on a runner that also hosted mongod. `grails-data-mongodb-core`'s test sources now need about 750 MB to compile, so a fresh fork dies with `OutOfMemoryError: Java heap space` in `compileTestGroovy`, and a lane passes only when Gradle happens to reuse an idle compiler daemon that another task started with the 2 GB heap. Dropping the override lets the shared `-Xmx2G` apply, as it does for the other sixty modules; the test forks keep their own `-Xmx1028M`. Report URL: https://github.com/apache/grails-core/actions/runs/40061613963 With regards, GitHub Actions via GitBox
