jamesfredley commented on PR #16158: URL: https://github.com/apache/grails-core/pull/16158#issuecomment-5332285835
CI on `ccca92fd4b` is fully green - no failures, only the usual publish/docs/JMH-on-PR jobs skipped. Closing the shard 0 question from the description. This run: | Job | Time | |---|---:| | Windows JDK 25 shard 0 | 1h 34m 51s | | Windows JDK 25 shard 1 | 44m 57s | | Windows JDK 25 shard 2 | 47m 39s | Shard 0 stays roughly 2x shards 1 and 2, which is the workload difference, not a regression: shard 0 runs `build` + `groovydoc` + `:grails-shell-cli:installDist` on top of its tests, while shards 1 and 2 run `testShard` only. `groovydoc` and `installDist` execute in the Gradle daemon, which never receives `-XX:ActiveProcessorCount`, so the cap cannot be the cause of that gap. The new forked-JVM assertions passed everywhere they run, so the flag is landing on real CI runners and not just locally. -- 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]
