disttask: refine planErr state transition

[ywqzzy]

What problem does this PR solve?

Issue Number: ref #49008

Problem Summary:
Previously when planErr and not retryable, the state transition is as follow:

1. pending->failed
2. pending->running->failed

What changed and how does it work?

We change the state transition to:

1. pending->reverting->reverted
2. pending->running->reverting->reverted

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 @ywqzzy. 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/test-infra repository.

[codecov]

Codecov Report

Merging #51279 (b5a2fad) into master (e06dc99) will decrease coverage by 15.3924%.
Report is 18 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51279         +/-   ##
=================================================
- Coverage   70.6260%   55.2337%   -15.3924%     
=================================================
  Files          1458       1569        +111     
  Lines        434160     606758     +172598     
=================================================
+ Hits         306630     335135      +28505     
- Misses       108287     248691     +140404     
- Partials      19243      22932       +3689     

Flag	Coverage Δ
integration	37.3247% <11.1111%> (?)
unit	70.8764% <100.0000%> (+0.4622%)	⬆️

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

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

[ywqzzy]

/retest

[tiprow]

@ywqzzy: 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/test-infra repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, okJiang

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 [D3Hunter,okJiang]
• pkg/disttask/OWNERS [D3Hunter]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-02-26 09:02:30.730389726 +0000 UTC m=+866239.478012837: ☑️ agreed by okJiang.
• 2024-02-27 05:17:45.668767251 +0000 UTC m=+939154.416390357: ☑️ agreed by D3Hunter.

[ywqzzy]

/retest

[tiprow]

@ywqzzy: 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/test-infra repository.