disttask: cancel subtask context if scheduled away

[tangenta]

What problem does this PR solve?

Issue Number: close #58450

Problem Summary: See #58450 (comment)

What changed and how does it work?

Cancel subtask context if scheduled away.

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 @tangenta. 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

Attention: Patch coverage is 57.89474% with 8 lines in your changes missing coverage. Please review.

Project coverage is 73.5652%. Comparing base (5934515) to head (6976bf3).
Report is 38 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58615        +/-   ##
================================================
+ Coverage   73.0744%   73.5652%   +0.4908%     
================================================
  Files          1676       1677         +1     
  Lines        463356     471804      +8448     
================================================
+ Hits         338595     347084      +8489     
+ Misses       103913     103619       -294     
- Partials      20848      21101       +253     

Flag	Coverage Δ
integration	42.8453% <0.0000%> (?)
unit	72.2902% <57.8947%> (+0.0302%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.1504% <ø> (-0.6580%)	⬇️

[D3Hunter]

rest lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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:

• 2025-01-06 07:35:17.931307047 +0000 UTC m=+166261.220138752: ☑️ agreed by D3Hunter.
• 2025-01-06 08:29:46.383273544 +0000 UTC m=+169529.672105247: ☑️ agreed by wjhuang2016.

[tiprow]

@tangenta: 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	8681e00	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.