-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Reset timeout to initial value #1739
Conversation
This is apparently the most probable casue of issue that tempted the fix redis#1718.
@HeartSaVioR @marcosnils Please review this. Once timeout is set to 1 second, tests with 1+ seconds of sleep are tend to fail. Resetting timeout should resolve this issue. |
@marcosnils @gkorland Please review this. |
jedis.close(); | ||
|
||
// reset config | ||
jedis = new Jedis("localhost", 6379); |
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.
I think it should be in a try-finally block
jedis.close(); | ||
|
||
// reset config | ||
jedis = new Jedis(new URI("redis://:foobared@localhost:6380/2")); |
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.
I think it should be in a try-finally block
@gkorland Just being lazy, but I think we can use |
LGTM!. Good catch @sazzad16 |
In two test methods, Redis config is changed but is not reset to initial value. Because of this,
redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of stream.
occurs time to time in tests. This PR will resolve this issue.