From 7485a0c1f7781030533bedc12a3d757bf4014dc6 Mon Sep 17 00:00:00 2001 From: Rob Bradford Date: Thu, 13 Feb 2020 17:20:43 +0000 Subject: [PATCH] Revert "build: Don't fail build on test_vfio failure" This reverts commit 014844d0daef115fb9b51ea8bdd9f6f596776653. Signed-off-by: Rob Bradford --- scripts/run_integration_tests.sh | 6 ------ src/main.rs | 1 - 2 files changed, 7 deletions(-) diff --git a/scripts/run_integration_tests.sh b/scripts/run_integration_tests.sh index 620b24e2d..f5d7d8154 100755 --- a/scripts/run_integration_tests.sh +++ b/scripts/run_integration_tests.sh @@ -184,12 +184,6 @@ time cargo test --features "integration_tests" "$@" -- --nocapture EOF RES=$? -# Try the VFIO test but ignore the result -newgrp kvm << EOF -export RUST_BACKTRACE=1 -time cargo test --features "integration_tests" test_vfio -- --nocapture --ignored -EOF - if [ $RES -eq 0 ]; then # virtio-mmio based testing cargo build --release --no-default-features --features "mmio" diff --git a/src/main.rs b/src/main.rs index 176736dca..86e3dc81a 100755 --- a/src/main.rs +++ b/src/main.rs @@ -3878,7 +3878,6 @@ mod tests { // its cloud-hypervisor host, we should be able to ssh into it, and verify // that it's running with the right kernel command line (We tag the command // line from cloud-hypervisor for that purpose). - #[cfg_attr(not(feature = "mmio"), ignore)] fn test_vfio() { test_block!(tb, "", { let mut clear = ClearDiskConfig::new();