New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cacher: when forgeting a watcher, call stopWatcherLocked multiple times #121615
cacher: when forgeting a watcher, call stopWatcherLocked multiple times #121615
Conversation
It's possible that the watcher is already not in the structure (e.g. in case of simultaneous Stop() and terminateAllWatchers(), but it is safe to call stopLocked() on a watcher multiple times.
Skipping CI for Draft Pull Request. |
/assign @wojtek-t |
/lgtm /kind bug |
LGTM label has been added. Git tree hash: c6ae6f33ff30a2feea2e2330572de2aca985c39f
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: p0lyn0mial, wojtek-t 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:
Approvers can indicate their approval by writing |
xref: #121438 |
@wojtek-t @p0lyn0mial this causing the CI to fail https://storage.googleapis.com/k8s-triage/index.html?ci=0&pr=1&job=unit , the test add is racy, I suggest we revert this /cc @liggitt
|
yes, i have opened #121645 to address the issue. i'm also okay with reverting the pr. |
@p0lyn0mial please send a revert just to unblock the CI, and work in parallel on the fix |
/triage accepted |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
It's possible that the watcher is already not in the structure (e.g. in case of simultaneous Stop() and terminateAllWatchers(), but it is safe to call stopLocked() on a watcher multiple times.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: