-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix flaky test JedisPoolTest.testCloseConnectionOnMakeObject #4138
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
Conversation
@thachlp |
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.
Thank @thachlp for helping me update the description.
Btw, I tried to run format and validate and it was successful, but it still fail on check-format job.
What do I miss? 🙇
Since code formatting was not enforced there are lots of discrepancies in the code. We are currently experimenting with how to enforce it. [Java Format Check] is optional currently and serves as a hint to reviewers that the code is not properly formatted. You can discard it for now. In case formatting the whole file introduces lots of additional formatting changes and makes the review harder my advice is to format only the modified code. Code formatting rules can be found PS: |
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.
LGTM
The test JedisPoolTest.testCloseConnectionOnMakeObject occasionally fails with the following error:
Root Cause:
The assertion is based on the output of getClientCount(jedis.clientList()), which is called immediately after closing a connection. However, Redis may take a short time to remove the closed connection from the client list, leading to a transient count mismatch and a flaky test result.
Example stack trace:
closes #4135