[close #355] chore: use latest gotestsum

pingyu commented 1 year ago

What problem does this PR solve?

Issue Number: close #355

Problem Description: ci: error obtaining VCS status: exit status 128

What is changed and how does it work?

Update to latest gotestsum.

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)

codecov[bot] commented 1 year ago

Codecov Report

Merging #354 (cf597aa) into main (c340278) will increase coverage by 0.0276%. Report is 2 commits behind head on main. The diff coverage is 63.7500%.

@@               Coverage Diff                @@
##               main       #354        +/-   ##
================================================
+ Coverage   61.1272%   61.1549%   +0.0276%     
================================================
  Files           240        241         +1     
  Lines         20261      20417       +156     
================================================
+ Hits          12385      12486       +101     
- Misses         6758       6811        +53     
- Partials       1118       1120         +2

Flag	Coverage Δ		*Carryforward flag
br	`60.6802% <ø> (ø)`		Carriedforward from c340278
cdc	`61.3720% <63.7500%> (+0.0379%)`	:arrow_up:

*This pull request uses carry forward flags. Click here to find out more.

Files	Coverage Δ
cdc/cdc/kv/client.go	`86.4748% <100.0000%> (+0.4517%)`	:arrow_up:
cdc/cdc/kv/metrics.go	`0.0000% <0.0000%> (ø)`
cdc/cdc/processor/pipeline/keyspan.go	`0.0000% <0.0000%> (ø)`
cdc/pkg/cmd/cli/cli_changefeed_update.go	`28.2051% <66.6666%> (+2.9877%)`	:arrow_up:
cdc/pkg/config/replica_config.go	`63.2653% <0.0000%> (-5.6236%)`	:arrow_down:
cdc/pkg/util/kv_filter.go	`91.6666% <91.6666%> (ø)`
cdc/cdc/processor/pipeline/puller.go	`0.0000% <0.0000%> (ø)`
cdc/cdc/kv/region_worker.go	`78.6885% <33.3333%> (-0.8949%)`	:arrow_down:
cdc/pkg/util/ctx.go	`76.4705% <0.0000%> (-12.1658%)`	:arrow_down:

... and 15 files with indirect coverage changes