fix(maven): de-flake maven e2e by dropping -X debug forks and widening timeout#36091
Merged
Conversation
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit 80efc64
☁️ Nx Cloud last updated this comment at |
b9d05f8 to
80efc64
Compare
AgentEnder
approved these changes
Jun 24, 2026
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.
Current Behavior
The
e2e/maven/src/maven.test.tscases "should build Maven project with dependencies without batch mode" and "should support targetNamePrefix option" intermittently time out (e.g.Command timed out after 600s: run app:install --no-batch).nx run <project>:install --no-batchfans the build out into one task per Maven lifecycle phase per module (~87 tasks), each spawning a freshmvnJVM that re-scans the whole reactor. That serial fan-out alone runs ~450-550s even with a warm~/.m2. Theinstallrun additionally passedverbose: true, which setsNX_VERBOSE_LOGGING=trueand makes every one of the ~87 forks runmvn -X(full debug) — a large amount of extra per-fork log I/O that pushed it over the previous 10-minute budget.Expected Behavior
installrun no longer passesverbose: true, so the ~87 forks don't each runmvn -X. The assertions (BUILD SUCCESS+ jar existence) don't need verbose output.--no-batchruns get a 15-minute timeout, comfortably above the inherent serial fan-out floor, so CI load no longer tips them over.Related Issue(s)
N/A — CI flake fix.
View session information ↗