-
Notifications
You must be signed in to change notification settings - Fork 762
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
deflake tracking-redir-broken test #1628
deflake tracking-redir-broken test #1628
Conversation
This address 2 issues: 1. It is possible (somehow) that the inner server client (r) was not working resp 3 when entering this test. this makes sure it does. 2. in case the test failed it might leave the redirection client closed. there is a cross test assumption it should be open, so moved most of the assert checks to the end of the test. Signed-off-by: Ran Shidlansik <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #1628 +/- ##
============================================
- Coverage 70.94% 70.85% -0.09%
============================================
Files 121 121
Lines 65132 65174 +42
============================================
- Hits 46207 46180 -27
- Misses 18925 18994 +69 |
assert {$res >= 0} | ||
# Consume PING reply | ||
assert_equal PONG [r read] |
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.
why this fail? Because the r is not in resp3?
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 suspect that it did somehow. maybe the 'r' is disconnected and reconnected at some point
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.
let's give it a try.
Signed-off-by: Ran Shidlansik <[email protected]>
This address 2 issues: 1. It is possible (somehow) that the inner server client (r) was not working resp 3 when entering this test. this makes sure it does. 2. in case the test failed it might leave the redirection client closed. there is a cross test assumption it should be open, so moved most of the assert checks to the end of the test. example fail: https://github.com/valkey-io/valkey/actions/runs/12979601179/job/36195523412 --------- Signed-off-by: Ran Shidlansik <[email protected]>
This address 2 issues:
It is possible (somehow) that the inner server client (r) was not working resp 3 when entering this test.
this makes sure it does.
in case the test failed it might leave the redirection client closed. there is a cross test assumption it should be open, so moved most of the assert checks to the end of the test.
example fail: https://github.com/valkey-io/valkey/actions/runs/12979601179/job/36195523412