Closed dependabot[bot] closed 8 months ago
@Ablu it looks like the CI now fails because of the virtio-queue
version we want to yank.
Should I apply this patch for now, or update vm-memory?
diff --git a/crates/vhost-user-backend/Cargo.toml b/crates/vhost-user-backend/Cargo.toml
index a3d0bbf..eceb611 100644
--- a/crates/vhost-user-backend/Cargo.toml
+++ b/crates/vhost-user-backend/Cargo.toml
@@ -16,7 +16,7 @@ libc = "0.2.39"
log = "0.4.17"
vhost = { path = "../vhost", version = "0.8", features = ["vhost-user-backend"] }
virtio-bindings = "0.2.1"
-virtio-queue = "0.9.0"
+virtio-queue = "=0.9.0"
vm-memory = { version = "0.12.0", features = ["backend-mmap", "backend-atomic"] }
vmm-sys-util = "0.11.0"
FYI the CI issue is not related to this PR, so this can go.
Superseded by #200.
Bumps rust-vmm-ci from
9751aaa
tobe28ad8
.Commits
be28ad8
test_coverage: fix formatting of --ignore-filename-regex0b9e2e2
Update container version to v284c55aa7
Updateexclude_path
description and examples9699b4d
test_coverage: put exclude_path value between double quotesb6483eb
test_coverage.py: fix formatting352bc23
Generate Cargo.lock before callcargo audit
Dependabot 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