-
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
Build(deps): Bump libvirt.org/go/libvirt from 1.10003.0 to 1.10005.0 #19279
Build(deps): Bump libvirt.org/go/libvirt from 1.10003.0 to 1.10005.0 #19279
Conversation
Bumps [libvirt.org/go/libvirt](https://gitlab.com/libvirt/libvirt-go-module) from 1.10003.0 to 1.10005.0. - [Commits](https://gitlab.com/libvirt/libvirt-go-module/compare/v1.10003.0...v1.10005.0) --- updated-dependencies: - dependency-name: libvirt.org/go/libvirt dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Hi @dependabot[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 Once the patch is verified, the new status will be reflected by the 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. |
Can one of the admins verify this patch? |
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 47.1s 51.2s 53.9s 49.8s 50.1s Times for minikube ingress: 26.0s 24.0s 27.5s 24.4s 28.0s docker driver with docker runtime
Times for minikube start: 22.6s 22.1s 24.8s 26.0s 25.1s Times for minikube ingress: 21.3s 21.8s 21.9s 21.8s 21.9s docker driver with containerd runtime
Times for minikube start: 24.4s 24.5s 24.4s 23.7s 23.5s Times for minikube ingress: 47.8s 48.9s 47.9s 48.3s 47.8s |
Here are the number of top 10 failed tests in each environments with lowest flake rate.
Besides the following environments also have failed tests:
To see the flake rates of all tests by environment, click here. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dependabot[bot], spowelljr 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 |
Bumps libvirt.org/go/libvirt from 1.10003.0 to 1.10005.0.
Commits
bcb3db5
Expose VIR_DOMAIN_LAUNCH_SECURITY_SEV_SNP_POLICY parameterc25623a
Re-generate API bindings for 10.5.0 release6872a7c
ci: refresh with latest lcitool manifestDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)