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
Use strict synchronization for revision getter to minimize flaky result caused by time racing. #17513
base: main
Are you sure you want to change the base?
Conversation
Hi @joshuazh-x. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
…lt caused by time racing. Signed-off-by: Joshua Zhang <joshuazh@microsoft.com>
50cf6cf
to
5a02f05
Compare
@joshuazh-x could you rebase this PR? |
var timeoutC <-chan time.Time | ||
if r.waitTimeout < math.MaxInt64 { | ||
timeoutC = time.After(r.waitTimeout) | ||
} |
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.
Suggest to follow the pattern "A Timeout of zero means no timeout.
"
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
for issue #17054 and #17487