[
https://issues.apache.org/jira/browse/GROOVY-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18137616#comment-18137616
]
ASF GitHub Bot commented on GROOVY-12685:
-----------------------------------------
testlens-app[bot] commented on PR #3203:
URL: https://github.com/apache/groovy/pull/3203#issuecomment-6617503721
## ✅ All tests passed ✅
🏷️ Commit: d1f6ccad9ac13d9e2e28b8622863ccb2ca7f1ccc
▶️ Tests: 127475 executed
⚪️ Checks: 26/26 completed
---
_Learn more about TestLens at
[testlens.app/docs](https://testlens.app/docs/features/pr-comment/)._
> Raise the heap of the forked compiler for the core test sources
> ---------------------------------------------------------------
>
> Key: GROOVY-12685
> URL: https://issues.apache.org/jira/browse/GROOVY-12685
> Project: Groovy
> Issue Type: Task
> Components: build
> Reporter: Scott Murphy Heiberg
> Priority: Major
>
> The forked compiler for the core test sources runs with {{groovycTest_mx=1g}}
> (gradle.properties). On master, {{:compileTestGroovy}} fails with "Java heap
> space" at 900m and passes at 1g, so there is little headroom: the
> closure-packing and closure-runtime fixes open as apache/groovy#3171 to #3202
> add enough test code that master plus all of them fails at 1g (three runs)
> and passes at 1100m. CI uses the default from gradle.properties, so landing
> that batch, or any other sizeable set of tests, will fail CI's test compile.
> Proposed: raise {{groovycTest_mx}} to 1536m. {{groovyJUnit_mx}} is already
> 2g, and the Gradle daemon's 2g is unaffected because the compiler runs in its
> own fork.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
