-
Notifications
You must be signed in to change notification settings - Fork 955
Try to stabilize aof test #2399
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
Signed-off-by: Sarthak Aggarwal <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## unstable #2399 +/- ##
============================================
- Coverage 71.49% 71.29% -0.20%
============================================
Files 123 123
Lines 67179 67179
============================================
- Hits 48028 47894 -134
- Misses 19151 19285 +134 🚀 New features to boost your workflow:
|
enjoy-binbin
left a comment
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.
ok, let give it a try
|
Please add to relevant projects for backporting. Flaky tests in old release branches is a pain too. |
|
I'm guessing we need this for 7.2, 8.0 and 8.1. Please change if I'm wrong. |
Based on @enjoy-binbin's suggestion on valkey-io#1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved valkey-io#1611 Signed-off-by: Sarthak Aggarwal <[email protected]>
|
@zuiderkwast does it need manual backports to those branches? I can help cherry-pick the change and raise a PR. |
|
So far, we've been backporting them when we're doing the next release. We just cherry-pick all of them into a PR and then we merge it without squashing the commits. We just look at the project board for each version under the to-be-backported column. I'm already picking this one to 8.0 in #2210. I'm reviving it. |
Based on @enjoy-binbin's suggestion on valkey-io#1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved valkey-io#1611 Signed-off-by: Sarthak Aggarwal <[email protected]> Signed-off-by: Viktor Söderqvist <[email protected]>
Based on @enjoy-binbin's suggestion on #1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved #1611 Signed-off-by: Sarthak Aggarwal <[email protected]> Signed-off-by: Viktor Söderqvist <[email protected]>
Based on @enjoy-binbin's suggestion on valkey-io#1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved valkey-io#1611 Signed-off-by: Sarthak Aggarwal <[email protected]> Signed-off-by: Viktor Söderqvist <[email protected]>
Based on @enjoy-binbin's suggestion on valkey-io#1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved valkey-io#1611 Signed-off-by: Sarthak Aggarwal <[email protected]>
Based on @enjoy-binbin's suggestion on valkey-io#1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved valkey-io#1611 Signed-off-by: Sarthak Aggarwal <[email protected]>
|
7.2 doesn't have this test case, so nothing to backport. |
Based on @enjoy-binbin's suggestion on #1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo. Resolved #1611 Signed-off-by: Sarthak Aggarwal <[email protected]>
Based on @enjoy-binbin's suggestion on #1611, I made the change to find the available port. The test has been passing in the daily tests in my local repo.
Some passed tests:
Resolved #1611