Skip to content

Conversation

minikube-bot
Copy link
Collaborator

The k8s-device-plugin project released a new k8s-device-plugin image

This PR was auto-generated by make update-nvidia-device-plugin-version using update-nvidia-device-plugin-version.yml CI Workflow.

@minikube-bot minikube-bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Sep 29, 2025
@k8s-ci-robot k8s-ci-robot requested review from nirs and prezha September 29, 2025 10:01
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Sep 29, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @minikube-bot. Thanks for your PR.

I'm waiting for a kubernetes 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/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 29, 2025
@k8s-ci-robot
Copy link
Contributor

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

Test name Commit Details Required Rerun command
pull-minikube-integration b9467c4 link true /test pull-minikube-integration

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 21652 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 43.4s    │ 45.1s                  │
│ enable ingress │ 15.8s    │ 16.0s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 45.2s 42.1s 45.1s 41.8s 42.7s
Times for minikube (PR 21652) start: 43.7s 46.2s 46.3s 45.0s 44.5s

Times for minikube ingress: 15.8s 15.9s 15.8s 15.8s 15.8s
Times for minikube (PR 21652) ingress: 15.3s 16.3s 15.8s 15.8s 16.8s

docker driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21652 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 22.0s    │ 21.5s                  │
│ enable ingress │ 12.2s    │ 13.0s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 20.9s 23.2s 22.2s 22.3s 21.4s
Times for minikube (PR 21652) start: 22.1s 20.9s 21.8s 21.4s 21.4s

Times for minikube ingress: 10.6s 11.6s 13.6s 12.6s 12.6s
Times for minikube (PR 21652) ingress: 15.6s 13.6s 12.6s 10.6s 12.6s

docker driver with containerd runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21652 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 19.8s    │ 20.5s                  │
│ enable ingress │ 26.3s    │ 23.1s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 20.8s 19.8s 18.9s 19.5s 19.9s
Times for minikube (PR 21652) start: 22.0s 20.1s 20.5s 20.5s 19.5s

Times for minikube ingress: 23.1s 23.1s 23.1s 23.1s 39.1s
Times for minikube (PR 21652) ingress: 23.1s 23.1s 23.1s 23.1s 23.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
Docker_Linux_crio_arm64 (1 failed) TestAddons/parallel/RegistryCreds(gopogh) Unknown
KVM_Linux_crio (1 failed) TestAddons/parallel/CSI(gopogh) 14.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestAddons/serial/Volcano(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestAddons/parallel/Registry(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestAddons/parallel/Ingress(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestAddons/parallel/LocalPath(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestAddons/parallel/Yakd(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestDockerEnvContainerd(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestFunctional/parallel/DashboardCmd(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestFunctional/parallel/ServiceCmdConnect(gopogh) 0.00% (chart)
Docker_Linux_containerd_arm64 (9 failed) TestFunctional/parallel/PersistentVolumeClaim(gopogh) 0.00% (chart)

Besides the following environments also have failed tests:

  • Docker_Linux_containerd: 20 failed (gopogh)

  • Docker_Linux_crio: 18 failed (gopogh)

  • Docker_Linux_docker_arm64: 12 failed (gopogh)

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

@medyagh
Copy link
Member

medyagh commented Sep 30, 2025

/lgtm

@medyagh medyagh merged commit de17596 into kubernetes:master Sep 30, 2025
37 of 51 checks passed
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 30, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: medyagh, minikube-bot

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants