Bump the memory-leak stress test heap so Gradle 9 script compilation fits on current runners - #742
Closed
takaharu-nakase wants to merge 1 commit into
Closed
Conversation
… current runners The stress test OOMs on run number 1 while compiling sample-groovy/buildSrc/build.gradle.kts, on unmodified main too, so 150M no longer fits the baseline footprint and the check fails for every PR. Co-Authored-By: Claude Fable 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 "Check for memory leaks" step (
counted-stress-test.sh 10 ./gradlew --daemon -Dorg.gradle.jvmargs="-Xmx150M") currently fails on run number 1, while compilingsample-groovy/buildSrc/build.gradle.kts— including on unmodifiedmain:main, unmodified workflow: https://github.com/takaharu-nakase/refreshVersions/actions/runs/30515593606 (OOM on run number 1)Since it fails before any repeated builds happen, this is not a leak being caught: the baseline footprint of Gradle 9's Kotlin DSL script compilation on current GitHub-hosted runners no longer fits in 150 MiB, so the check now fails for every PR (e.g. #741). The last green run of this workflow dates back a while (main: 2025-08-16, last PR re-run: 2026-07-01), which matches an environment drift on the runner side rather than a regression in this repository.
This PR bumps the cap to 256 MiB, which keeps the check meaningful (10 successive builds in the same daemon must still fit a fixed budget, so monotonic leaks still blow up) while giving script compilation enough headroom.
Verified on my fork with unmodified plugin code + this workflow change: https://github.com/takaharu-nakase/refreshVersions/actions/runs/30515882804 — "Check plugins", "Check sample-kotlin", "Check for memory leaks" and "Check sample-groovy" all pass.
Note: in that verification run, the dispatch-only "Check sample-multi-modules" step (always skipped on pull_request events) fails with a pre-existing Kotlin compilation error in
sample-multi-modules/buildSrcon unmodifiedmain— unrelated to this change.🤖 Generated with Claude Code