ci: force the jvm test leg fully serial to fix intermittent OOM hangs - #1264
Merged
Merged
Conversation
The jvm leg runs nearly every module's jvmTest sequentially, each forking its own 8g-heap Test JVM. ci-gradle.properties already caps org.gradle.workers.max at 2 repo-wide, but on this leg two 8g forks plus the 4g Gradle client JVM can still exceed the 16 GB runner. develop's PR #1262 merge commit hit this twice in a row (test (jvm) silently hanging ~30-40 min before the 40-min timeout force-cancelled it) - the same "operation was canceled" signature this leg was already split out to avoid, just needing the extra thread/heap pressure SKEEP-005's new concurrency tests added to tip it over. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The jvm leg runs nearly every module's jvmTest sequentially, each forking its own 8g-heap Test JVM. ci-gradle.properties already caps org.gradle.workers.max at 2 repo-wide, but on this leg two 8g forks plus the 4g Gradle client JVM can still exceed the 16 GB runner. develop's PR #1262 merge commit hit this twice in a row (test (jvm) silently hanging ~30-40 min before the 40-min timeout force-cancelled it) - the same "operation was canceled" signature this leg was already split out to avoid, just needing the extra thread/heap pressure SKEEP-005's new concurrency tests added to tip it over.