Shut down executor threads after timeout to prevent JaCoCo EOFException#1303
Open
Shut down executor threads after timeout to prevent JaCoCo EOFException#1303
Conversation
When executeMain times out, awaitTermination returns but worker threads remain running (non-daemon). For remote DBs like Materialize, threads blocked on network I/O prevent the JVM from exiting cleanly, causing surefire to forcibly kill the process before JaCoCo can flush jacoco.exec, resulting in an EOFException during report generation. Calling shutdownNow() after the timeout interrupts threads (PostgreSQL JDBC socket reads respond to Thread.interrupt()), allowing them to exit and JaCoCo to write complete coverage data. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
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.
When executeMain times out, awaitTermination returns but worker threads remain running (non-daemon). For remote DBs like Materialize, threads blocked on network I/O prevent the JVM from exiting cleanly, causing surefire to forcibly kill the process before JaCoCo can flush jacoco.exec, resulting in an EOFException during report generation.
Calling shutdownNow() after the timeout interrupts threads (PostgreSQL JDBC socket reads respond to Thread.interrupt()), allowing them to exit and JaCoCo to write complete coverage data.