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
build: update to klog v2.70.1 #111001
build: update to klog v2.70.1 #111001
Conversation
This makes ktesting more resilient against logging from leaked goroutines, which is a problem that came up in kubelet node shutdown tests (kubernetes#110854).
/assign @dims |
@pohly: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/approve Small update to klog to fix something we got wrong. |
/retest Some overall flakiness, test cluster didn't come up? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, liggitt, pohly 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 |
/retest |
/remove-sig api-machinery |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind bug
/kind failing-test
What this PR does / why we need it:
This makes ktesting more resilient against logging from leaked goroutines,
which is a problem that came up in kubelet node shutdown
tests (#110854).
Which issue(s) this PR fixes:
Related-To: #110854 - a more complete fix of that test would be to not leak goroutines
Does this PR introduce a user-facing change?