-
Notifications
You must be signed in to change notification settings - Fork 127
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
Fixed failing unit test #610
Fixed failing unit test #610
Conversation
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! Thanks
Signed-off-by: Martin Gaievski <[email protected]>
434670f
5d0e467
to
434670f
Compare
Codecov Report
@@ Coverage Diff @@
## main #610 +/- ##
============================================
- Coverage 84.73% 84.47% -0.26%
+ Complexity 1055 1050 -5
============================================
Files 149 149
Lines 4291 4291
Branches 379 379
============================================
- Hits 3636 3625 -11
- Misses 480 489 +9
- Partials 175 177 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
At first glance issue with rolling upgrades may be caused by some recent change in core transport code. I've made some test runs and logged issue for core opensearch-project/OpenSearch#5065 |
As per reply from core team 2.4 is not compatible with 3.0 builds, the plan is to port some changes in next 2.x to make next 2.x release (presumably 2.5 ) compatible with main/3.0. Until then bwc in CI will keep failing |
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.
Overall, it seems we are easing the test by giving minimum number instead of specific number for a method to be invoked. Could you justify the change?
Right, so depending on the sequence of method execution mock cluster can be in a different states, and that may or may not trigger additional serialization/deserialization calls, and this influence the number of method calls. Particular number of calls isn't essential for this test, we just want to make sure call to the knnvector format got intercepted and out implementation executed. |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-610-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ca49f73e8fcccc41a86e607b254ae10840aace62
# Push it to GitHub
git push --set-upstream origin backport/backport-610-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
Signed-off-by: Martin Gaievski [email protected]
Description
Fixed flaky unit tests, narrow assertion logic and adjust for test runs with multi node mock cluster
Rolling upgrades are failing, presumable due to issue with security plugin opensearch-project/security#2228
Repro for certain seeds:
After change test runs are succesful:
Issues Resolved
[List any issues this PR will resolve]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.