TestThread: Try interrupt() before stop() in tearDown() #8169
+20
−4
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
This PR improves
TestThread.tearDown()to tryinterrupt()before falling back toThread.stop(), as suggested by @cpovirk in #7319.Changes:
interrupt()first, allowing interruptible threads (like those inInterruptibleMonitorTest) to clean up gracefullyDUE_DILIGENCE_MILLIS(100ms) for the thread to respond to the interruptstop()if the thread is still alive after the interrupt attemptMotivation
The existing implementation immediately tries
Thread.stop()via reflection, which:UnsupportedOperationExceptionon Java 20+Many test threads (particularly in
InterruptibleMonitorTest) are designed to respond to interrupts. By tryinginterrupt()first, we allow these threads to terminate cleanly without relying on the deprecatedstop()method.Behavior by Java Version
Testing
Verified locally that existing tests pass:
InterruptibleMonitorTest- 16 tests ✅UninterruptibleMonitorTest- 16 tests ✅UninterruptiblesTest- 49 tests ✅Related Issues
Fixes #7319