scripts: limit integration tests to cloud-hypervisor package

Pass `-p cloud-hypervisor` to all `cargo nextest run` invocations in
the integration test scripts so test discovery and execution are
scoped to the cloud-hypervisor package only, avoiding running tests
from other workspace crates.

This avoids flooding the output messages like below
`test result: ok. 0 passed; 0 failed; 0 ignored;
0 measured; 0 filtered out; finished in 0.00s
Running unittests src/lib.rs`

Signed-off-by: Muminul Islam <muislam@microsoft.com>
This commit is contained in:
Muminul Islam
2026-05-06 12:55:53 -07:00
committed by Rob Bradford
parent 0ca06517f8
commit df1809c1fa
7 changed files with 17 additions and 17 deletions

View File

@@ -33,12 +33,12 @@ export RUST_BACKTRACE=1
export RUSTFLAGS="$RUSTFLAGS"
# Run VFIO tests using legacy vfio interface with container/group
time cargo nextest run --retries 3 --no-tests=pass --test-threads=1 "vfio::test_nvidia" -- ${test_binary_args[*]}
time cargo nextest run -p cloud-hypervisor --retries 3 --no-tests=pass --test-threads=1 "vfio::test_nvidia" -- ${test_binary_args[*]}
RES=$?
# Run VFIO tests using vfio cdev interface backed by iommufd
if [ $RES -eq 0 ]; then
time cargo nextest run --retries 3 --no-tests=pass --test-threads=1 "vfio::test_iommufd" -- ${test_binary_args[*]}
time cargo nextest run -p cloud-hypervisor --retries 3 --no-tests=pass --test-threads=1 "vfio::test_iommufd" -- ${test_binary_args[*]}
RES=$?
fi