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
[1.21] Fix CI #4961
[1.21] Fix CI #4961
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert 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 |
/test critest_fedora |
1 similar comment
/test critest_fedora |
f825472
to
e3168bf
Compare
Codecov Report
@@ Coverage Diff @@
## release-1.21 #4961 +/- ##
================================================
+ Coverage 40.17% 43.22% +3.04%
================================================
Files 115 107 -8
Lines 9311 9847 +536
================================================
+ Hits 3741 4256 +515
+ Misses 5154 5141 -13
- Partials 416 450 +34 |
e3168bf
to
9b6f4e5
Compare
/retest |
@haircommander PTAL, GitHub actions are green again |
/lgtm |
/test e2e_fedora |
/retest Please review the full test history for this PR and help us cut down flakes. |
/hold until containers/conmon#268 merges |
@saschagrunert: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
This should make the CI green again on 1.21.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?