You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pekko.apache.org by fa...@apache.org on 2026/09/11 21:19:16 UTC
(pekko-connectors-kafka) branch main updated: increase CI heap so the binary-compatibility check does not run out of memory (#654)
This is an automated email from the ASF dual-hosted git repository.
pjfanning pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pekko-connectors-kafka.git
The following commit(s) were added to refs/heads/main by this push:
new 9e660c85 increase CI heap so the binary-compatibility check does not run out of memory (#654)
9e660c85 is described below
commit 9e660c85ce7cb3e7ed8c7e89f132742c31c3102c
Author: PJ Fanning <pj...@users.noreply.github.com>
AuthorDate: Fri Sep 11 22:19:10 2026 +0100
increase CI heap so the binary-compatibility check does not run out of memory (#654)
Motivation:
The `Check Code Style` job, which runs `checkCodeStyle; mimaReportBinaryIssues`,
fails with `java.lang.OutOfMemoryError: Java heap space`. sbt runs with its
default 1g heap and spends most of the job in GC before dying:
[warn] In the last 10 seconds, 24.282 (253.1%) were spent in GC.
[Heap: 0.00GB free of 1.00GB, max 1.00GB]
java.lang.OutOfMemoryError: Java heap space
[error] [launcher] error during sbt launcher: java.lang.OutOfMemoryError
The unscoped `mimaReportBinaryIssues` loads current and previous classfiles for
every module in one JVM, so it is the peak consumer. This is not specific to any
one PR - `main` has failed the same way on every run since #652.
Modification:
Set `JAVA_OPTS: "-Xmx4g"` in the workflow-level `env` block of the CI workflow,
so every job in it gets a 4g heap. 4g matches what this repository already uses
for its other heavy sbt jobs (`link-validator.yml`, `publish-*-docs.yml`), and
is well inside the memory available on the GitHub-hosted runners.
This is deliberately confined to the CI workflow rather than `.sbtopts`, so
local sbt runs keep whatever heap the developer has configured.
Result:
The binary-compatibility check completes instead of exhausting the heap, and the
`Check / Binary Compatibility` job can pass again.
Tests:
- Not run - CI configuration only; the change is verified by the CI run on this
PR, which is the job that was failing.
References:
Refs #653 - that PR is blocked by this same pre-existing failure
---
.github/workflows/check-build-test.yml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.github/workflows/check-build-test.yml b/.github/workflows/check-build-test.yml
index 7c1adeb6..8f847753 100644
--- a/.github/workflows/check-build-test.yml
+++ b/.github/workflows/check-build-test.yml
@@ -18,6 +18,9 @@ concurrency:
env:
PEKKO_TEST_TIMEFACTOR: 10.0
EVENT_NAME: ${{ github.event_name }}
+ # sbt otherwise runs with a 1g heap, which the unscoped `mimaReportBinaryIssues`
+ # run in the Check Code Style job exhausts
+ JAVA_OPTS: "-Xmx4g"
jobs:
check-code-style:
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org