-
Notifications
You must be signed in to change notification settings - Fork 6k
ci: Add cluster test for vector search #61009
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
ci: Add cluster test for vector search #61009
Conversation
Signed-off-by: “EricZequan” <[email protected]>
Hi @EricZequan. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cc @breezewish Since the latest release of tiflash does not include pingcap/tiflash#10103, some tests of this PR still fail, but other tests have been verified locally. I will continue to follow up on this issue. |
Signed-off-by: “EricZequan” <[email protected]>
Ref: PingCAP-QE/ci#3502 |
cd - || exit 1 | ||
|
||
echo "Starting TiUP Playground in the background..." | ||
tiup playground nightly --db=1 --kv=1 --tiflash=1 --db.binpath=../../bin/tidb-server & |
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.
- how to use it in release branches in feature?
- how to use it in CI jobs in pull requests of
tiflash
repo?
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.
How to test against a possible command like tiflash=pr/xxxx
?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #61009 +/- ##
================================================
+ Coverage 73.1624% 74.4256% +1.2631%
================================================
Files 1726 1729 +3
Lines 479299 490202 +10903
================================================
+ Hits 350667 364836 +14169
+ Misses 107134 104159 -2975
+ Partials 21498 21207 -291
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Signed-off-by: “EricZequan” <[email protected]>
/test ? |
@purelind: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@purelind: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
||
function start_tidb_latest() { | ||
echo "Starting TiUP Playground in the background..." | ||
tiup playground nightly --db=1 --kv=1 --tiflash=1 & |
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 do we need to use nightly to start the cluster instead of using the previously built binary?
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.
Only run_upgrade_test.sh will use this func. The test performed by this script is to build vector data under a fixed version of tidb and tiflash, and then upgrade the version to test compatibility. Here we first use the newest release for testing, and then will change it to a certain version (such as 8.5.0) later.
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 also think this is wrong. @EricZequan The upgrade test should test whether old version can be upgraded to the PR version, because PR version is going to be "latest". So you should start the cluster using v8.5.1 first, then start using PR version.
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 add the way of starting v8.5.1 and nightly version, PTAL~
/hold |
Signed-off-by: “EricZequan” <[email protected]>
Signed-off-by: “EricZequan” <[email protected]>
../../bin/tidb-server -V | ||
echo | ||
echo "+ TiKV Version" | ||
~/.tiup/components/tikv/v9.0.0-beta.1.pre-nightly/tikv-server --version |
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.
This will be broken after TiDB switch the tag?
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.
tikv are fixed and not be broken after change the tag. But tidb and tiflash exist this problem, I will try to fix it after @purelind giving some dependency
Relate to pingcap/tidb#61009 Add new vector search test presubmit job. The test is currently in the testing phase and will not be triggered automatically; it can only be triggered manually.
/test ? |
@EricZequan: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
||
cd - || exit 1 | ||
|
||
echo "Starting TiUP Playground in the background..." |
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.
the nightly tiup package has hours latency, how to test it with refreshed tikv and tiflash binaries?
and how to to test it with next-gen tidb binaries?
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.
As long as it is nightly, it is fine, because we are mainly testing the impact of tidb commit on vector, and we only need to keep tidb up to date.
In addition, how to use next-gen tidb is being discussed with @purelind
tiup tidb:v8.5.1 -V | ||
echo | ||
echo "+ TiKV Version" | ||
tiup tikv:v8.5.1 --version | ||
echo |
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 it should be hard coded?
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.
In the upgrade test, we will use the v8.5.1 cluster. This cluster has been cached, so we can directly output its version.
/retest |
/retest |
1 similar comment
/retest |
/test pull-tiflash-integration-test |
@purelind: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/retest |
1 similar comment
/retest |
Signed-off-by: “EricZequan” <[email protected]>
/test pull-tiflash-integration-test |
@EricZequan: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: “EricZequan” <[email protected]>
/test pull-tiflash-integration-test |
@EricZequan: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[LGTM Timeline notifier]Timeline:
|
/hold for a while to see whether others have more comments |
/retest |
@wuhuizuo: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bb7133, breezewish, winoros, wuhuizuo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
What problem does this PR solve?
Issue Number: close #61017
Problem Summary:
What changed and how does it work?
Run some e2e tests for each PR to test vector search.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.