The GitHub Actions job "Validate GitHub Actions" on 
grails-core.git/fix/docs-out-of-gradle-daemon has failed.
Run started by GitHub user jdaugherty (triggered by jdaugherty).

Head commit for run:
5d347efc384eed926a1f6888baa76f8458a9f401 / James Daugherty <[email protected]>
build: address review of the documentation fork

- A -PgroovydocMaxHeapSize / -PguideMaxHeapSize override now beats whatever a
  build script set, so the two aggregates and the guide - the runs that can
  actually run out of heap - can be got moving from the command line. The
  per-task ext property they used went the other way and could not be
  overridden at all; the aggregates now use the typed groovydocEnhancer
  extension instead, and the 1g default moves out of gradle.properties, where
  it would have clamped them.

- The guide worker was handed no AntBuilder, so DocPublisher built its own,
  which logs at INFO: sixteen [mkdir]/[copy]/[unjar] lines that Gradle used to
  route to its hidden INFO level now reached the console. Both forks take their
  Ant log level from the build's instead - quiet by default, and INFO under
  --info, where those diagnostics have always lived.

- The guide worker heap gets the same treatment as groovydoc: 1500m rather than
  1g (it settles under a gigabyte resident) and a project property to raise it.

- The runner script's classpath stream is closed, and a missing script now
  fails with a message instead of an NPE inside leftShift.

- The heap test asserted only that the output contained 'Process', which almost
  any build failure satisfies; it now asserts the JVM's own "Too small maximum
  heap". A second test covers the override precedence, and two cover the Ant
  log level.

- The out-of-memory advice in AGENTS.md, CONTRIBUTING.md and both skills said
  `GRADLE_OPTS="-Xms2G -Xmx5G"`, which does not size the daemon at all while
  org.gradle.jvmargs is set in gradle.properties. All four now agree on
  -Dorg.gradle.jvmargs=-Xmx4G and say why.

Report URL: https://github.com/apache/grails-core/actions/runs/35739872862

With regards,
GitHub Actions via GitBox

Reply via email to