-
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
cri-dockerd 0.2.6 #14827
cri-dockerd 0.2.6 #14827
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 |
@spowelljr : it was not entirelly obvious how to kick off the build of the new binaries, so just updated version and checksums |
This comment was marked as outdated.
This comment was marked as outdated.
No worries, I just ran the job |
ok-to-build-iso |
ok-to-build-image |
This comment was marked as outdated.
This comment was marked as outdated.
ok-to-build-image |
Hi @afbjorklund, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
This comment was marked as outdated.
This comment was marked as outdated.
cacff5e
to
7cff141
Compare
ok-to-build-image |
ok-to-build-iso |
Hi @afbjorklund, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
Commenting to subscribe to the PR. I really need this to go through in order to advance on my project. |
The commit is only needed for patching, but leave it for now. Make sure to use the version too, in the cri-dockerd command.
33d779e
to
8a9f917
Compare
ok-to-build-iso |
ok-to-build-image |
Hi @afbjorklund, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
kvm2 driver with docker runtime
Times for minikube start: 55.0s 52.9s 54.4s 53.1s 53.9s Times for minikube ingress: 27.6s 28.6s 29.6s 28.2s 25.2s docker driver with docker runtime
Times for minikube start: 26.1s 24.7s 25.4s 25.9s 25.0s Times for minikube ingress: 19.9s 18.9s 48.9s 20.0s 19.5s docker driver with containerd runtime
Times for minikube start: 21.3s 22.5s 22.0s 21.6s 24.0s Times for minikube ingress: 25.9s 26.5s 27.4s 26.4s 26.5s |
kvm2 driver with docker runtime
Times for minikube ingress: 29.7s 29.7s 29.3s 28.2s 28.7s Times for minikube start: 52.9s 53.9s 54.0s 55.6s 53.5s docker driver with docker runtime |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
@afbjorklund: PR needs rebase. 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. |
go1.19
Use cni by default on Linux, too
Note: needs fix for
--network-plugin
to go in first: