workerpool: fix block on Tune when all workers finished

[D3Hunter]

What problem does this PR solve?

Issue Number: close #59267

Problem Summary:

What changed and how does it work?

• also consider ctx.Done when sending events

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

[tangenta]

Why this change?

[D3Hunter]

not sure why, my local make lint; make bazel_prepare change it automatically. reverted

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 5 lines in your changes missing coverage. Please review.

Project coverage is 74.8358%. Comparing base (fc8bdb5) to head (b24b16e).
Report is 3 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59271        +/-   ##
================================================
+ Coverage   73.0496%   74.8358%   +1.7861%     
================================================
  Files          1689       1735        +46     
  Lines        466978     475669      +8691     
================================================
+ Hits         341126     355971     +14845     
+ Misses       104890      97260      -7630     
- Partials      20962      22438      +1476     

Flag	Coverage Δ
integration	48.7864% <0.0000%> (?)
unit	72.2581% <50.0000%> (+0.0263%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	60.3251% <ø> (+14.8993%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, 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 [tangenta,wjhuang2016]
• pkg/ddl/OWNERS [tangenta,wjhuang2016]
• pkg/resourcemanager/OWNERS [tangenta,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-02-06 08:05:40.600356414 +0000 UTC m=+345412.132768412: ☑️ agreed by wjhuang2016.
• 2025-02-06 09:40:03.049565081 +0000 UTC m=+351074.581977064: ☑️ agreed by tangenta.

[joechenrh]

/cherry-pick release-8.5

[ti-chi-bot]

@joechenrh: new pull request created to branch release-8.5: #61927.
But this PR has conflicts, please resolve them!

In response to this:

/cherry-pick release-8.5

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 ti-community-infra/tichi repository.