*: test PR for infoschema

[joechenrh]

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary:

What changed and how does it work?

Check List

Tests

• [ ] Unit test
• [ ] Integration test
• [ ] Manual test (add detailed scripts or steps below)
• [ ] No need to test

  • [ ] I checked and no code files have been changed.

Side effects

• [ ] Performance regression: Consumes more CPU
• [ ] Performance regression: Consumes more Memory
• [ ] Breaking backward compatibility

Documentation

• [ ] Affects user behaviors
• [ ] Contains syntax changes
• [ ] Contains variable changes
• [ ] Contains experimental features
• [ ] Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot[bot]]

[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 tangenta, xuhuaiyu for approval, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• pkg/ddl/OWNERS
• pkg/domain/OWNERS
• pkg/expression/OWNERS
• pkg/infoschema/OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[tiprow[bot]]

Hi @joechenrh. 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.

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.

[joechenrh]

/ok-to-test

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 74.5753%. Comparing base (aade0ee) to head (8f141d1). :warning: Report is 1903 commits behind head on master.

:warning: Current head 8f141d1 differs from pull request most recent head 75dcc1a

Please upload reports for the commit 75dcc1a to get more accurate results.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #56668        +/-   ##
================================================
+ Coverage   73.4169%   74.5753%   +1.1584%     
================================================
  Files          1629       1674        +45     
  Lines        450073     458068      +7995     
================================================
+ Hits         330430     341606     +11176     
+ Misses        99369      94841      -4528     
- Partials      20274      21621      +1347     

Flag	Coverage Δ
integration	45.2724% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	∅ <ø> (∅)
parser	∅ <ø> (∅)
br	62.2796% <ø> (+16.0374%)	:arrow_up:

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot[bot]]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{:open_book: For more info, you can check the "Contribute Code" section in the development guide.}

---

Notice: To remove the do-not-merge/needs-tests-checked label, please finished the tests then check the finished items in description.

For example:

Tests

• [x] Unit test
• [ ] Integration test
• [ ] Manual test (add detailed scripts or steps below)
• [ ] No code

_{:open_book: For more info, you can check the "Contribute Code" section in the development guide.}

[ti-chi-bot[bot]]

@joechenrh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test build
idc-jenkins-ci-tidb/check_dev	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test check-dev
pull-unit-test-ddlv1	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test pull-unit-test-ddlv1
idc-jenkins-ci-tidb/unit-test	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev_2	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test check-dev2
pull-lightning-integration-test	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test pull-lightning-integration-test
pull-br-integration-test	8f141d1b5cf30920e284f4afba9ffb6702a11d1b	link	true	/test pull-br-integration-test
pull-integration-realcluster-test-next-gen	75dcc1a76d3fc287877aed9d2cdb4991a775f74c	link	true	/test pull-integration-realcluster-test-next-gen

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.