[fix #430] pin gocov to v1.1.0 and remove duplicate install step in CDC CI

[Copilot]

cdc-unit-test CI job was failing because gocov@latest introduced a breaking change. The explicit install step in the workflow was also a duplicate of what the Makefile already handles.

What problem does this PR solve?

Problem Description: cdc/tools/Makefile installed gocov@latest, causing non-reproducible builds and CI failures. The CI workflow also had a redundant explicit install step.

What is changed and how does it work?

• cdc/tools/Makefile: pin gocov from @latest → @v1.1.0
• .github/workflows/ci-cdc.yml: remove the standalone "install gocov" step — make unit_test_in_verify_ci already invokes the Makefile's gocov target which now installs the pinned version

Code changes

• No code

Check List for Tests

This PR has been tested by at least one of the following methods:

• No code

Side effects

• No side effects

Related changes

• No related changes

To reviewers

Please follow these principles to check this pull requests:

• Concentration. One pull request should only do one thing. No matter how small it is, the change does exactly one thing and gets it right. Don't mix other changes into it.
• Tests. A pull request should be test covered, whether the tests are unit tests, integration tests, or end-to-end tests. Tests should be sufficient, correct and don't slow down the CI pipeline largely.
• Functionality. The pull request should implement what the author intends to do and fit well in the existing code base, resolve a real problem for TiDB/TiKV users. To get the author's intention and the pull request design, you could follow the discussions in the corresponding GitHub issue or internal.tidb.io topic.
• Style. Code in the pull request should follow common programming style. (For Go, we have style checkers in CI). However, sometimes the existing code is inconsistent with the style guide, you should maintain consistency with the existing code or file a new issue to fix the existing code style first.
• Documentation. If a pull request changes how users build, test, interact with, or release code, you must check whether it also updates the related documentation such as READMEs and any generated reference docs. Similarly, if a pull request deletes or deprecates code, you must check whether or not the corresponding documentation should also be deleted.
• Performance. If you find the pull request may affect performance, you could ask the author to provide a benchmark result.

(The above text mainly refers to TiDB Development Guide. It's also highly recommended to read about Writing code review comments)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>add unit test step in cdc ci workflow</issue_title>
<issue_description>the unit test command is make unit_test_in_verify_ci, also upload the coverage data to codecov.io after. the codecov token var name should be set as TIKV_MIGRATION_CODECOV_TOKEN.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes add unit test step in cdc ci workflow #430

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[ti-chi-bot]

Hi @Copilot. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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]

@copilot please fix the ci failure include the "dco", please re-commit all your commit with signoff

[ti-chi-bot]

/test ?

[wuhuizuo]

/test pull-integration-test

[wuhuizuo]

/test pull-unit-test

[ti-chi-bot]

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

Details

In response to this:

/test pull-integration-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.

[wuhuizuo]

/run-all-tests

[ti-chi-bot]

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

Details

In response to this:

/test pull-unit-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.

[Copilot]

@copilot please fix the ci failure include the "dco", please re-commit all your commit with signoff

All new commits now include the Signed-off-by trailer (see commits 2778e80 and c49ec80). The two earlier unsigned commits (3c3b4b9, 3cbe125) remain in the branch history but cannot be amended without a force push. If the DCO check still fails due to those older commits, the PR could be squash-merged to resolve it.

[Copilot]

@copilot install gocov with v1.1.0

Updated gocov to v1.1.0 in commit eca099c, signed off.

[wuhuizuo]

@copilot looks like we can remove the install gocov tool action step to avoid duplicate

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.1610%. Comparing base (d6003dc) to head (bd578b6).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@               Coverage Diff                @@
##               main       #431        +/-   ##
================================================
+ Coverage   62.0761%   62.1610%   +0.0848%     
================================================
  Files           247        247                
  Lines         21174      21203        +29     
================================================
+ Hits          13144      13180        +36     
+ Misses         6820       6816         -4     
+ Partials       1210       1207         -3     

Flag	Coverage Δ		*Carryforward flag
br	60.5927% <ø> (ø)		Carriedforward from 73c8606
cdc	62.8355% <ø> (+0.1201%)	⬆️

*This pull request uses carry forward flags. Click here to find out more.
see 10 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ti-chi-bot]

@Copilot: 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
pull-integration-test	bd578b6	link	true	/test pull-integration-test
pull-unit-test	bd578b6	link	true	/test pull-unit-test

Full PR test history. Your PR dashboard.

Details

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.

[pingyu]

LGTM~