pingcap
Release-testing: v9.0.0-beta.1 tiflow repo CI trigger
What problem does this PR solve?
Issue Number: close #xxx
What is changed and how it works?
Check List
Tests
- Unit test
- Integration test
- Manual test (add detailed scripts or steps below)
- No code
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.
If you don't think this PR needs a release note then fill it with `None`.
[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 lance6716 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}
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 55.1589%. Comparing base (
b679430) to head (0a0768f).
:x: Your project check has failed because the head coverage (55.1589%) is below the target coverage (60.0000%). You can increase the head coverage or adjust the target coverage.
Additional details and impacted files
| Components | Coverage Δ | |
|---|---|---|
| cdc | 59.4003% <ø> (+0.0467%) |
:arrow_up: |
| dm | 50.1785% <ø> (+0.0652%) |
:arrow_up: |
| engine | 53.2505% <ø> (+0.0282%) |
:arrow_up: |
| Flag | Coverage Δ | |
|---|---|---|
| unit | 55.1589% <ø> (+0.0474%) |
:arrow_up: |
Flags with carried forward coverage won't be shown. Click here to find out more.
@@ Coverage Diff @@
## release-9.0-beta.1 #12094 +/- ##
==========================================================
+ Coverage 55.1114% 55.1589% +0.0474%
==========================================================
Files 1030 1030
Lines 143197 143197
==========================================================
+ Hits 78918 78986 +68
+ Misses 58482 58427 -55
+ Partials 5797 5784 -13
:rocket: New features to boost your workflow:
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
![codecov[bot] avatar](https://avatars.githubusercontent.com/in/254?v=4 "Published by a pub.dev verified publisher"){kind=small}
@stevenayu: The following commands are available to trigger required jobs:
/test pull-cdc-integration-kafka-test
/test pull-cdc-integration-mysql-test
/test pull-cdc-integration-pulsar-test
/test pull-cdc-integration-storage-test
/test pull-dm-compatibility-test
/test pull-dm-integration-test
/test pull-engine-integration-test
/test pull-syncdiff-integration-test
/test pull-verify
Use /test all to run all jobs.
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.
/test pull-cdc-integration-kafka-test pull-cdc-integration-mysql-test pull-cdc-integration-pulsar-test pull-cdc-integration-storage-test pull-dm-compatibility-test pull-dm-integration-test pull-engine-integration-test pull-syncdiff-integration-test pull-verify
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: 2025-03-13 15:46:51.
/test pull-cdc-integration-kafka-test pull-cdc-integration-mysql-test pull-cdc-integration-pulsar-test pull-cdc-integration-storage-test pull-dm-compatibility-test pull-dm-integration-test pull-engine-integration-test pull-syncdiff-integration-test pull-verify
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: 2025-03-13 15:49:27.
@joccau: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:
/test pull-cdc-integration-kafka-test
/test pull-cdc-integration-mysql-test
/test pull-cdc-integration-pulsar-test
/test pull-cdc-integration-storage-test
/test pull-dm-compatibility-test
/test pull-dm-integration-test
/test pull-engine-integration-test
/test pull-syncdiff-integration-test
/test pull-verify
Use /test all to run all jobs.
In response to this:
/test pull-dm-compatibility-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.
/test pull-cdc-integration-kafka-test pull-cdc-integration-mysql-test pull-cdc-integration-pulsar-test pull-cdc-integration-storage-test pull-dm-compatibility-test pull-dm-integration-test pull-engine-integration-test pull-syncdiff-integration-test pull-verify pull-dm-compatibility-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: 2025-03-20 19:21:03.
