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
logcheck update and golangci-lint integration #108159
Conversation
/lgtm |
/test pull-kubernetes-unit |
/skip |
/approve /assign @liggitt (needs root OWNERS approval) |
/retest |
1 similar comment
/retest |
/retest (not sure if it helps!) |
/retest TestCheckRetryClosesBody flake. |
fwiw, the flaky unit test is getting skipped in #108981 until we resolve the issue had one low priority comment about a change to the config logging escaping/garbling the config file content - #108159 (comment) - won't block this PR on it, but I'm pretty sure that change makes that log line very unusable |
/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 |
/remove-sig api-machinery |
/retest |
@pohly: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The updated logcheck finds additional problems and thanks to the integration into golangci-lint runs more efficiently and correctly (didn't check staging before).
Which issue(s) this PR fixes:
Fixes #106746, #108854, #106276, #105841, kubernetes/klog#214
Special notes for your reviewer:
The lack of tagging for logcheck is tracked in kubernetes/klog#312
Does this PR introduce a user-facing change?