tikv
scheduler: skip evict-leader-scheduler when setting schedule deny label
This commit comes from https://github.com/tikv/pd/commit/463297be6a621183386105525e0aa33a5fc09ebd.patch
DO NOT MERGE
What problem does this PR solve?
For testing
Issue Number: Close #xxx
What is changed and how does it work?
PD FIX
Check List
Tests
- Unit test
- Integration test
- Manual test (add detailed scripts or steps below) x
- No code
Code changes
- Has the configuration change
- Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
- Has persistent data change
Side effects
- Possible performance regression
- Increased code complexity
- Breaking backward compatibility
Related changes
- PR to update
pingcap/docs/pingcap/docs-cn: - PR to update
pingcap/tiup: - Need to cherry-pick to the release branch
Release note
Nothing
NOT FOR RELEASE
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign lhy1024 for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![ti-chi-bot[bot] avatar](https://avatars.githubusercontent.com/in/214286?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @HaoW30. Thanks for your PR.
I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.
Now you can start all CI jobs with /test all in comment or query the triggers with /test ?
@HaoW30: The /test command needs one or more targets.
The following commands are available to trigger required jobs:
/test build
/test integration-copr-test
Use /test all to run the following jobs that were automatically triggered:
tikv/pd/release-8.1/ghpr_build
In response to this:
/test
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.
@rleungx: The /test command needs one or more targets.
The following commands are available to trigger required jobs:
/test build
/test integration-copr-test
Use /test all to run the following jobs that were automatically triggered:
tikv/pd/release-8.1/ghpr_build
In response to this:
/test
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.
According to https://github.com/tikv/pd/blob/feature/release-7.5.1-20241126/.github/workflows/pd-tests.yaml#L10-L16, the branch name does not match the format.
@HaoW30: The /test command needs one or more targets.
The following commands are available to trigger required jobs:
/test build
/test integration-copr-test
Use /test all to run the following jobs that were automatically triggered:
tikv/pd/release-8.1/ghpr_build
In response to this:
/test
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.
