Repository navigation
Fix out of memory errors with big JUnit 4 suites (#3511) - #3515
Merged
Merged
Conversation
Since 3.6.0 JUnit 3/4 projects run on the Vintage engine, and with one fork all test classes went into a single launch, keeping the whole test plan in memory. Run them one class at a time again, like 3.5.x did (unless classes run in parallel). Also forget a test's id once it has passed or been skipped. Only failed tests need to keep theirs for reruns. Signed-off-by: Olivier Lamy <olamy@apache.org>
olamy
force-pushed
the
JUnitPlatformProvider-memory
branch
from
October 8, 2026 20:56
eb4646e to
7dc502e
Compare
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
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.
Since 3.6.0 JUnit 3/4 projects run on the Vintage engine, and with
one fork all test classes went into a single launch, keeping the
whole test plan in memory. Run them one class at a time again, like
3.5.x did (unless classes run in parallel).
Also forget a test's id once it has passed or been skipped. Only
failed tests need to keep theirs for reruns.
Signed-off-by: Olivier Lamy olamy@apache.org
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
check one of the following: