-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Upgrade crio to 1.17.3 #8922
Upgrade crio to 1.17.3 #8922
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund 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 |
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.
do you mind pulling upstream so this PR gets tested with ISO test?
#8851
ae47e46
to
265d388
Compare
The build worked, but the tests failed. Now what ? How do I know that they passed with 1.17.1 before ? "NumberOfTests": 200, "NumberOfFail": 4, "NumberOfPass": 187, "NumberOfSkip": 9, "FailedTests": [ "TestRunningBinaryUpgrade", "TestStoppedBinaryUpgrade", "TestFunctional/parallel/TunnelCmd/serial/WaitService/IngressIP", "TestFunctional/parallel/TunnelCmd/serial/AccessDirect" ] |
valid questions. |
There is a 1.17.4 out (and 1.18.3 and 1.19.0RC1, but those require an OS upgrade for the newer go version) |
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.
My guess is that the test failures are flakes and unrelated to the ISO change. I'm going to merge this, build the ISO and open a separate PR to test it @ HEAD.
No description provided.