You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@grails.apache.org by ma...@apache.org on 2026/09/22 12:17:00 UTC
(grails-core) branch ci/macos-skip-docs-8.0.x created (now b57e7a22f2)
This is an automated email from the ASF dual-hosted git repository.
matrei pushed a change to branch ci/macos-skip-docs-8.0.x
in repository https://gitbox.apache.org/repos/asf/grails-core.git
at b57e7a22f2 ci: skip the documentation build on the macOS runner
This branch includes the following new commits:
new b57e7a22f2 ci: skip the documentation build on the macOS runner
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(grails-core) 01/01: ci: skip the documentation build on the macOS runner
Posted by ma...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
matrei pushed a commit to branch ci/macos-skip-docs-8.0.x
in repository https://gitbox.apache.org/repos/asf/grails-core.git
commit b57e7a22f219129d84d5e4caa640b3a85394ae7c
Author: Mattias Reichel <ma...@gmail.com>
AuthorDate: Tue Sep 22 14:16:30 2026 +0200
ci: skip the documentation build on the macOS runner
The macOS job runs the full documentation chain (aggregateGroovydoc followed by
publishGuide) inside the Gradle daemon, and on the 3 CPU / 7 GB macos-latest
runner the daemon's 5 GB heap is regularly exhausted once publishGuide starts.
Over the last eight days 19 of 70 completed macOS jobs failed with
OutOfMemoryError: Java heap space in that chain, including four runs of the
8.0.x branch itself, and even the successful jobs took two to five hours
against roughly 75 minutes for the same tasks on Ubuntu.
Drop groovydoc from the macOS task list and exclude :grails-doc:docs so the
job builds and tests on Apple silicon without producing documentation that the
Ubuntu JDK 21/25 and Windows shard 0 jobs already build.
---
.github/workflows/gradle.yml | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/gradle.yml b/.github/workflows/gradle.yml
index 36f415cf88..6a8d273f3e 100644
--- a/.github/workflows/gradle.yml
+++ b/.github/workflows/gradle.yml
@@ -141,7 +141,12 @@ jobs:
- os: macos-latest
java: 21
job_name: macOS JDK 21
- gradle_task: 'build :grails-shell-cli:installDist groovydoc'
+ # No groovydoc here, and :grails-doc:docs is excluded below: the documentation
+ # chain (aggregateGroovydoc followed by publishGuide, both running inside the
+ # daemon) exhausts the 5 GB daemon heap on this runner, and the Ubuntu and
+ # Windows shard 0 jobs already build the same docs. This job exists to run the
+ # build and tests on Apple silicon.
+ gradle_task: 'build :grails-shell-cli:installDist'
# The macOS runner has ~7 GB of RAM and 3 CPUs, against ~16 GB and 4 CPUs on the
# Linux and Windows runners, while org.gradle.jvmargs still asks for a 5 GB daemon
# (groovydoc needs it). Capping only maxTestParallel would not help: that is a
@@ -151,7 +156,7 @@ jobs:
# setting that actually limits concurrent test and compiler JVMs; maxTestParallel
# is kept alongside it so no single task exceeds that cap either. This reduces
# memory pressure on the smallest runner rather than proving the job fits.
- runner_arguments: '--max-workers=2 -PmaxTestParallel=2'
+ runner_arguments: '--max-workers=2 -PmaxTestParallel=2 -x :grails-doc:docs'
cache_writer: true
- os: windows-latest
java: 25