Closed AilinKid closed 1 week ago
Hi @AilinKid. Thanks for your PR.
PRs from untrusted users cannot be marked as trusted with /ok-to-test
in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all
.
I understand the commands that are listed here.
/ok-to-test
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 73.5078%. Comparing base (
26e3b5f
) to head (b0d2612
). Report is 15 commits behind head on master.
/test tidb_parser_test
@AilinKid: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test build
/test check-dev
/test check-dev2
/test mysql-test
/test pull-br-integration-test
/test pull-integration-ddl-test
/test pull-lightning-integration-test
/test pull-mysql-client-test
/test unit-test
The following commands are available to trigger optional jobs:
/test canary-notify-when-compatibility-sections-changed
/test pingcap/tidb/canary_ghpr_unit_test
/test pull-common-test
/test pull-e2e-test
/test pull-integration-common-test
/test pull-integration-copr-test
/test pull-integration-jdbc-test
/test pull-integration-mysql-test
/test pull-integration-nodejs-test
/test pull-sqllogic-test
/test pull-tiflash-test
Use /test all
to run the following jobs that were automatically triggered:
pingcap/tidb/ghpr_build
pingcap/tidb/ghpr_check
pingcap/tidb/ghpr_check2
pingcap/tidb/ghpr_mysql_test
pingcap/tidb/ghpr_unit_test
pingcap/tidb/pull_integration_ddl_test
pingcap/tidb/pull_mysql_client_test
/test fast_test_tiprow
@AilinKid: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test build
/test check-dev
/test check-dev2
/test mysql-test
/test pull-br-integration-test
/test pull-integration-ddl-test
/test pull-lightning-integration-test
/test pull-mysql-client-test
/test unit-test
The following commands are available to trigger optional jobs:
/test canary-notify-when-compatibility-sections-changed
/test pingcap/tidb/canary_ghpr_unit_test
/test pull-common-test
/test pull-e2e-test
/test pull-integration-common-test
/test pull-integration-copr-test
/test pull-integration-jdbc-test
/test pull-integration-mysql-test
/test pull-integration-nodejs-test
/test pull-sqllogic-test
/test pull-tiflash-test
Use /test all
to run the following jobs that were automatically triggered:
pingcap/tidb/ghpr_build
pingcap/tidb/ghpr_check
pingcap/tidb/ghpr_check2
pingcap/tidb/ghpr_mysql_test
pingcap/tidb/ghpr_unit_test
pingcap/tidb/pull_integration_ddl_test
pingcap/tidb/pull_mysql_client_test
/test all
// while for now, we still can not push the sort prop to the intersection index plan side, temporarily banned here.
if !prop.IsSortItemEmpty() && candidate.path.IndexMergeIsIntersection {
return invalidTask, nil
}
intersection case shouldn't pay too much attention of keep-order, because it's already been banned when converting plans
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Defined2014, winoros
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Timeline:
2024-04-29 09:17:57.669339031 +0000 UTC m=+262431.426474597
: :ballot_box_with_check: agreed by Defined2014.2024-05-06 09:40:55.288450704 +0000 UTC m=+868609.045586277
: :ballot_box_with_check: agreed by winoros.In response to a cherrypick label: new pull request created to branch release-8.1
: #53149.
What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tidb/issues/52947
Problem Summary: https://github.com/pingcap/tidb/issues/52947#issuecomment-2082033877
What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.