Conversation
The JaCoCo report goal intermittently fails with EOFException when the forked test JVM is force-killed before the agent can finish flushing jacoco.exec. This has been especially visible on QPG/Materialize and other remote-DBMS jobs where long-lived worker threads continue past test completion. The report isn't uploaded or consumed anywhere in CI — it's generated and discarded — so skip it with -Djacoco.skip=true. Developers can still produce coverage locally by running mvn test without the flag. Co-Authored-By: Claude Opus 4.6 <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.
Summary
-Djacoco.skip=trueto everymvn ... testinvocation in.github/workflows/main.ymlmvn -B package/mvn -B verifysteps untouchedEOFExceptionfromjacoco:reportwhen the forked test JVM is force-killed before the agent finishes flushingjacoco.execWhy this route
PR #1303 (and its follow-up with daemon-thread pools) addressed one plausible root cause — non-daemon worker threads keeping the forked JVM alive past surefire's 30 s exit grace. Re-runs showed the EOFException still reproducing on the QPG Materialize job even with those fixes, so something else is preventing the fork from exiting cleanly (likely surefire 2.22.2's fork-booter behavior, or a non-daemon thread in the JDBC driver / backend we're testing against).
Since the JaCoCo report is generated but not uploaded or consumed anywhere in CI, skipping it removes the flaky failure entirely. Developers can still produce coverage locally with
mvn test.Test plan
🤖 Generated with Claude Code