-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Add logging for reconciler unit test #111577
Add logging for reconciler unit test #111577
Conversation
/retest |
/assign @saad-ali |
/assign @gnufied Can you take a look at this PR? I think adding some logging in the unit tests will help troubleshoot these flakes which are infrequent, but have been happening for a long time. |
/priority important-soon |
/sig storage |
/approve |
@msau42: The provided milestone is not valid for this repository. Milestones in this repository: [ Use In response to this:
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. |
/milestone v1.26 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brianpursley, msau42 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 |
What type of PR is this?
/kind flake
What this PR does / why we need it:
#107414 is a persistent unit test flake, but it is difficult to reproduce locally and difficult to troubleshoot by examining the failure logs, in part because of the way unit test calls the same verify functions multiple times and the context of when it fails is not clear.
I'm proposing with this PR to add some additional logging into the verify functions of the reconciler unit tests to help troubleshoot this flake.
Which issue(s) this PR 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.: