Release-testing: v8.5.0 tidb repo CI trigger

[stevenayu]

release-test trigger for version 8.5.0

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]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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]

[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 zz-jason for approval. 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

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

[tiprow]

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

[stevenayu]

/test ?

[ti-chi-bot]

@stevenayu: The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

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.

[stevenayu]

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2024-11-22 19:10:13.

[ti-chi-bot]

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:10:13.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

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.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:10:13.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:10:13.

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.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-8.5@5c55cb4). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.5     #57639   +/-   ##
================================================
  Coverage               ?   57.6101%           
================================================
  Files                  ?       1795           
  Lines                  ?     634413           
  Branches               ?          0           
================================================
  Hits                   ?     365486           
  Misses                 ?     243749           
  Partials               ?      25178           

Flag	Coverage Δ
integration	39.3112% <ø> (?)
unit	72.5003% <ø> (?)

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

Components	Coverage Δ
dumpling	52.9478% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	62.9884% <0.0000%> (?)

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[stevenayu]

/test all

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

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

[stevenayu]

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2024-11-22 19:33:02.

[ti-chi-bot]

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:33:02.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:33:02.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:33:02.

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.

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.

[stevenayu]

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2024-11-22 19:34:22.

[ti-chi-bot]

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:34:22.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:34:22.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:34:22.

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.

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.

[stevenayu]

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2024-11-22 19:37:27.

[ti-chi-bot]

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:37:27.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:37:27.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 19:37:27.

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.

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.

[stevenayu]

/test pull-br-integration-test pull-common-test pull-e2e-test pull-integration-common-test pull-integration-copr-test pull-integration-ddl-test pull-integration-e2e-test pull-integration-jdbc-test pull-integration-mysql-test pull-integration-nodejs-testpull-integration-python-orm-test pull-integration-tidb-tools-test pull-lightning-integration-test pull-mysql-client-test pull-sqllogic-test pull-tiflash-test

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test pull-br-integration-test pull-common-test pull-e2e-test pull-integration-common-test pull-integration-copr-test pull-integration-ddl-test pull-integration-e2e-test pull-integration-jdbc-test pull-integration-mysql-test pull-integration-nodejs-testpull-integration-python-orm-test pull-integration-tidb-tools-test pull-lightning-integration-test pull-mysql-client-test pull-sqllogic-test pull-tiflash-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.

[stevenayu]

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2024-11-22 20:19:02.

[ti-chi-bot]

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 20:19:02.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 20:19:02.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 20:19:02.

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.

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.

[stevenayu]

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2024-11-22 20:19:54.

[ti-chi-bot]

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 20:19:54.

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.

[tiprow]

@stevenayu: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 20:19:54.

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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

@stevenayu: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test pull-unit-test-ddlv1

/test unit-test

The following commands are available to trigger optional jobs:

/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-e2e-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-nodejs-test

/test pull-integration-python-orm-test

/test pull-integration-tidb-tools-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/release-8.5/pull_build

pingcap/tidb/release-8.5/pull_check

pingcap/tidb/release-8.5/pull_check2

pingcap/tidb/release-8.5/pull_mysql_test

pingcap/tidb/release-8.5/pull_unit_test

In response to this:

/test

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the /test CI FT test.
Commented on: 2024-11-22 20:19:54.

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.

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]

@stevenayu: 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
wip/pull-integration-e2e-test	aea949f	link	false	/test pull-integration-e2e-test
pull-integration-common-test	aea949f	link	false	/test pull-integration-common-test
pull-integration-tidb-tools-test	aea949f	link	false	/test pull-integration-tidb-tools-test
pull-integration-jdbc-test	aea949f	link	false	/test pull-integration-jdbc-test

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