Skip to content

Conversation

@minikube-bot
Copy link
Collaborator

The crictl project released a new version

This PR was auto-generated by make update-crictl-version using update-crictl-version.yml CI Workflow.

@minikube-bot
Copy link
Collaborator Author

ok-to-build-image

@minikube-bot
Copy link
Collaborator Author

ok-to-build-iso

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Nov 18, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: minikube-bot
Once this PR has been reviewed and has the lgtm label, please assign comradeprogrammer for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 18, 2025
@k8s-ci-robot k8s-ci-robot requested review from medyagh and nirs November 18, 2025 22:03
@k8s-ci-robot
Copy link
Contributor

Hi @minikube-bot. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 18, 2025
@medyagh
Copy link
Member

medyagh commented Nov 18, 2025

ok-to-build-image

@minikube-bot
Copy link
Collaborator Author

Hi @minikube-bot, 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.

@minikube-bot
Copy link
Collaborator Author

Hi @minikube-bot, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further.

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 19, 2025
@medyagh
Copy link
Member

medyagh commented Nov 19, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 19, 2025
@k8s-ci-robot
Copy link
Contributor

@minikube-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
integration-kvm-crio-linux-x86-64 af8f791 link true /test integration-kvm-crio-linux-x86-64
integration-kvm-containerd-linux-x86-64 af8f791 link true /test integration-kvm-containerd-linux-x86-64
integration-docker-crio-linux-x86-64 af8f791 link true /test integration-docker-crio-linux-x86-64
integration-none-docker-linux-x86-64 af8f791 link true /test integration-none-docker-linux-x86-64
integration-docker-containerd-linux-x86-64 af8f791 link true /test integration-docker-containerd-linux-x86-64

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

@minikube-pr-bot
Copy link

kvm2 driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21924 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 41.0s    │ 41.9s                  │
│ enable ingress │ 16.3s    │ 16.7s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 40.7s 40.4s 43.0s 41.0s 39.8s
Times for minikube (PR 21924) start: 41.2s 39.1s 44.3s 40.8s 43.9s

Times for minikube ingress: 15.2s 14.7s 15.8s 19.7s 16.3s
Times for minikube (PR 21924) ingress: 15.8s 15.8s 19.8s 15.8s 16.2s

docker driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21924 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 23.8s    │ 22.9s                  │
│ enable ingress │ 11.4s    │ 11.0s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 25.1s 24.3s 24.5s 22.2s 22.7s
Times for minikube (PR 21924) start: 22.5s 22.7s 25.3s 23.0s 21.0s

Times for minikube ingress: 10.6s 10.6s 10.6s 12.6s 12.6s
Times for minikube (PR 21924) ingress: 12.6s 10.6s 10.6s 10.6s 10.6s

docker driver with containerd runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21924 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 20.2s    │ 20.4s                  │
│ enable ingress │ 20.1s    │ 20.1s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 19.6s 23.2s 18.9s 19.6s 19.5s
Times for minikube (PR 21924) start: 19.7s 20.1s 18.9s 20.8s 22.6s

Times for minikube ingress: 20.1s 20.1s 20.1s 20.1s 20.1s
Times for minikube (PR 21924) ingress: 20.1s 20.1s 20.1s 20.1s 20.1s

@minikube-pr-bot
Copy link

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment Test Name Flake Rate
KVM_Linux_crio (1 failed) TestAddons/parallel/CSI(gopogh) 14.00% (chart)
Docker_Linux_containerd (5 failed) TestKubernetesUpgrade(gopogh) 0.00% (chart)
Docker_Linux_containerd (5 failed) TestStartStop/group/old-k8s-version/serial/DeployApp(gopogh) 0.00% (chart)
Docker_Linux_containerd (5 failed) TestStartStop/group/no-preload/serial/DeployApp(gopogh) 0.00% (chart)
Docker_Linux_containerd (5 failed) TestStartStop/group/embed-certs/serial/DeployApp(gopogh) 0.00% (chart)
Docker_Linux_containerd (5 failed) TestStartStop/group/default-k8s-diff-port/serial/DeployApp(gopogh) 2.00% (chart)
Docker_Windows (1 failed) TestErrorSpam/setup(gopogh) Unknown
Docker_Linux_containerd_arm64 (4 failed) TestStartStop/group/old-k8s-version/serial/DeployApp(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (4 failed) TestStartStop/group/no-preload/serial/DeployApp(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (4 failed) TestStartStop/group/embed-certs/serial/DeployApp(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (4 failed) TestStartStop/group/default-k8s-diff-port/serial/DeployApp(gopogh) 0.00% (chart)

Besides the following environments also have failed tests:

  • Docker_Linux_crio: 37 failed (gopogh)

  • Docker_Linux_crio_arm64: 36 failed (gopogh)

To see the flake rates of all tests by environment, click here.

@medyagh medyagh merged commit 47029b5 into kubernetes:master Nov 19, 2025
36 of 54 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants