br/cdcutil: don't skip failed changefeeds

[YuJuncen]

What problem does this PR solve?

Issue Number: close #53131

Problem Summary:
A failed changefeed won't be checked during restore, if the user resume it then, the changefeed may need to scan many data load by BR.

What changed and how does it work?

Now, we will also check the checkpoint ts of a failed changefeed. This may be a little different from old versions, but given backup ts is usually long long ago, I think this won't be really harmful.

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

[tiprow]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.5713%. Comparing base (0afe54d) to head (e6ad355).
Report is 4 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53482        +/-   ##
================================================
+ Coverage   72.5326%   74.5713%   +2.0386%     
================================================
  Files          1505       1527        +22     
  Lines        429866     438064      +8198     
================================================
+ Hits         311793     326670     +14877     
+ Misses        98774      90843      -7931     
- Partials      19299      20551      +1252     

Flag	Coverage Δ
integration	50.6203% <50.0000%> (?)
unit	71.3335% <100.0000%> (-0.0865%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.3858% <ø> (+9.0124%)	⬆️

[YuJuncen]

/retest

[tiprow]

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

In response to this:

/retest

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]

[LGTM Timeline notifier]

Timeline:

• 2024-05-22 09:59:30.242180198 +0000 UTC m=+2252123.999315770: ☑️ agreed by sdojjy.
• 2024-05-22 10:36:47.600839693 +0000 UTC m=+2254361.357975267: ☑️ agreed by BornChanger.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, D3Hunter, sdojjy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BornChanger,D3Hunter,sdojjy]
• lightning/OWNERS [D3Hunter]

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

[tiprow]

@YuJuncen: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	e6ad355	link	true	/test fast_test_tiprow

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.