DanielLeens commented on PR #11198: URL: https://github.com/apache/seatunnel/pull/11198#issuecomment-5151192132
I checked the new run after `7dd25753`: https://github.com/srijan-singh/seatunnel/actions/runs/30693530415/job/91352609088 The failure moved to `Run / unit-test (8, windows-latest)`, but it is still the same root cause: ```text project seatunnel-ci-tools There was an error in the forked process GC overhead limit exceeded ``` The latest workflow change did not apply the fix in the best place. It currently sets: ```yaml MAVEN_OPTS: -Xmx2g -Dfile.encoding=UTF-8 JAVA_TOOL_OPTIONS: -Xmx2g -XX:MaxMetaspaceSize=512m ``` `JAVA_TOOL_OPTIONS` is too broad because it affects every Java process in the job, and `2g` is still not enough for this `seatunnel-ci-tools` Surefire fork. Also, lowering `MAVEN_OPTS` from the previous `4g` to `2g` is not helpful here. Please update the `unit-test` command itself and pass heap to Surefire via Maven `argLine`, then remove `JAVA_TOOL_OPTIONS`. For example: ```yaml - name: run all modules unit test run: | ./mvnw -B -T 1 clean verify \ -DskipUT=false \ -DskipIT=true \ -D"license.skipAddThirdParty"=true \ -D"skip.ui"=true \ -DargLine="-Xmx3072m -XX:MaxMetaspaceSize=512m -Dfile.encoding=UTF-8" \ --no-snapshot-updates env: MAVEN_OPTS: -Xmx4096m -Dfile.encoding=UTF-8 ``` This keeps the change CI-only and targets the Surefire test JVM directly. Please do not change the Couchbase connector code for this failure. -- 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]
