-
Notifications
You must be signed in to change notification settings - Fork 44
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
test: improve logging for flaky TestCRD test #1347
test: improve logging for flaky TestCRD test #1347
Conversation
/assign @karlkfi |
I think #1342 will fix the flakiness in TestCRDDeleteBeforeRemoveCustomResourceV1, but I'm not 100% sure. |
Nope, nevermind. THIS should fix it: #1348 |
This test has become increasingly flaky. Increasing the reconciler log level should help surface more of the reconciler logs when the test fails.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
TestCRDDeleteBeforeRemoveCustomResourceV1 is still flaky. More logs would be useful for diagnosis.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nan-yu 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 |
fe8eb2c
into
GoogleContainerTools:main
This test has become increasingly flaky. Increasing the reconciler log level should help surface more of the reconciler logs when the test fails.