statistics: try to fix pseudo

[hawkingrei]

trafficstars

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 ask for approval from hawkingrei. For more information see the Kubernetes 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

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

[codecov[bot]]

Codecov Report

:x: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review. :white_check_mark: Project coverage is 72.1264%. Comparing base (28cb579) to head (413f18f). :warning: Report is 4778 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #49142        +/-   ##
================================================
+ Coverage   71.0454%   72.1264%   +1.0810%     
================================================
  Files          1368       1405        +37     
  Lines        402969     414795     +11826     
================================================
+ Hits         286291     299177     +12886     
- Misses        96737      96801        +64     
+ Partials      19941      18817      -1124     

Flag	Coverage Δ
integration	44.3886% <83.3333%> (?)
unit	71.0454% <ø> (ø)

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

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	52.4529% <ø> (-0.5185%)	:arrow_down:

: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.

[hawkingrei]

/test all

[hawkingrei]

/test tiprow_fast_test

[ti-chi-bot[bot]]

@hawkingrei: 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 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-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-ddl-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-lightning-integration-test
• /test pull-mysql-client-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

In response to this:

/test tiprow_fast_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/test-infra repository.

[hawkingrei]

/test mysql-test

[tiprow[bot]]

@hawkingrei: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test mysql-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/test-infra repository.

[hawkingrei]

/test mysql-test

[tiprow[bot]]

@hawkingrei: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test mysql-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/test-infra repository.

[hawkingrei]

/retest all

[ti-chi-bot[bot]]

@hawkingrei: The /retest command does not accept any targets. The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-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-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-ddl-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-lightning-integration-test
• /test pull-mysql-client-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

In response to this:

/retest all

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/test-infra repository.

[tiprow[bot]]

@hawkingrei: The /retest command does not accept any targets. The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/retest all

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/test-infra repository.

[hawkingrei]

/test mysql-test

[tiprow[bot]]

@hawkingrei: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test mysql-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/test-infra repository.

[hawkingrei]

/test all

[hawkingrei]

/test mysql-test

[tiprow[bot]]

@hawkingrei: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test mysql-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/test-infra repository.

[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]]

PR needs rebase.

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/test-infra repository.

[ti-chi-bot[bot]]

@hawkingrei: 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/check_dev_2	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test check-dev
idc-jenkins-ci-tidb/mysql-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test mysql-test
idc-jenkins-ci-tidb/build	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test build
idc-jenkins-ci-tidb/unit-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test unit-test
pull-mysql-client-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-mysql-client-test
pull-integration-ddl-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-integration-ddl-test
pull-br-integration-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-br-integration-test
pull-lightning-integration-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-lightning-integration-test
pull-integration-e2e-test	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-integration-e2e-test
pull-integration-realcluster-test-next-gen	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-integration-realcluster-test-next-gen
pull-unit-test-next-gen	413f18f21c1bb2c03ceb2e765be30ed5bd4ef268	link	true	/test pull-unit-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.