-
Notifications
You must be signed in to change notification settings - Fork 11.1k
TestThread: Try interrupt() before stop() in tearDown() #8169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nickita-khylkouski
wants to merge
2
commits into
google:master
Choose a base branch
from
nickita-khylkouski:fix-testthread-teardown-interrupt
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+20
−4
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Do not use Thread.stop. A recommended way to stop one thread from another is to have the first thread poll a boolean field that is initially false but can be set to true by the second
thread to indicate that the first thread is to stop itself. Because reading and
writing a boolean field is atomic, some programmers dispense with synchronization when accessing the field:" - Item 78 of Effective Java programming (3rd edition).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review! A couple of important points about context:
This PR doesn't introduce
Thread.stop()— the existing code already calls it. This PR actually reduces reliance on it by tryinginterrupt()first.The boolean polling pattern from Effective Java Item 78 can't apply here.
TestThreadis used in concurrency tests where threads are deliberately blocked inside synchronization primitives (Monitor.enter(),Condition.await(), etc.). A thread suspended in a native blocking call cannot poll a boolean field — it's not in a loop.The Guava maintainers already addressed this in the existing TODO comment, noting that some threads are in uninterruptible operations intentionally and there is no other way to clean them up. The long-term plan is to drop
stop()once Java 20+ is the minimum.This PR implements the approach suggested by @cpovirk in #7319: try
interrupt()first, keepstop()as a fallback only for older JDKs.