-
Notifications
You must be signed in to change notification settings - Fork 128
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
Update bwc version after 2.9 release #1002
Update bwc version after 2.9 release #1002
Conversation
Signed-off-by: Junqiu Lei <[email protected]>
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
@junqiu-lei not sure if this change fixes the BWC tests, as I can see the tests in the github actions are failing. |
@navneet1v The BWC tests error is unrelated to this PR:
The error is same as the Geospatial plugin one fixed in the PR. I can help to raise a PR later to fix it. |
can we merge in those changes, as this is not very difficult to know why the tests are not passing. |
5a49190
to
f586df1
Compare
Codecov Report
@@ Coverage Diff @@
## main #1002 +/- ##
============================================
- Coverage 85.37% 85.13% -0.24%
+ Complexity 1146 1141 -5
============================================
Files 154 154
Lines 4683 4683
Branches 423 423
============================================
- Hits 3998 3987 -11
- Misses 495 504 +9
- Partials 190 192 +2
|
@junqiu-lei I can still see BWC tests failing. Please check |
There is a new error on the BWC CI:
|
It is failing because k-NN plugin might not be present in the new artifact, 2.10 |
@junqiu-lei plugins are not added in the manifest 2.10.0. So, the artifact don't have the plugins and the BWC tests are failing |
Please fix the DCO check |
Looks like infra team will help to add all components to manifest. cc @prudhvigodithi opensearch-project/opensearch-build@8fb3588 And also we need merge the 2.x PR BWC bump: #979 |
@junqiu-lei Can you also pls fix the Developer Certificate of Origin Check. I think if we don't fix it now, it will cause the DCO check on future PRs also to fail. |
Signed-off-by: Junqiu Lei <[email protected]>
f586df1
to
01c4e91
Compare
Thanks @naveentatikonda, added DCO |
The CI failure is expected to fail as k-NN component still not added to manifest 2.10.0. |
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-1002-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8c79385330d80d225460a713effbaa039aaa886a
# Push it to GitHub
git push --set-upstream origin backport/backport-1002-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 |
Will manually raise PR to fix the core refactor to 2.x and then merge #979 |
Description
Update versions after 2.9 release: change 2.9.0-SNAPSHOT to 2.9.0, add 2.10.0-SNAPSHOT.
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.