cloud-hypervisor/scripts/run_unit_tests.sh

#!/bin/bash

source $HOME/.cargo/env

BUILD_TARGET=${BUILD_TARGET-x86_64-unknown-linux-gnu}
cargo_args=("$@")
[ $(uname -m) = "aarch64" ] && cargo_args+=("--no-default-features")
[ $(uname -m) = "aarch64" ] && cargo_args+=("--features kvm")

export RUST_BACKTRACE=1
cargo test --target $BUILD_TARGET --workspace ${cargo_args[@]} || exit 1;
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-07-16 09:54:33 +00:00			`#!/bin/bash`

			`source $HOME/.cargo/env`

ci: Pass target triple to the test scripts We pass it to the integration and unit tests script through --libc. Cargo tests are left unmodified. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2020-04-21 06:02:58 +00:00			`BUILD_TARGET=${BUILD_TARGET-x86_64-unknown-linux-gnu}`
unit tests: Fix unit tests and docs for AArch64 Currently, not every feature of the cloud-hypervisor is enabled on AArch64, which means that on AArch64 machines, the `run_unit_tests.sh` needs to be tailored and some unit test cases should be run on x86_64 only. Also this commit fixes the typo and unifies `Arm64` and `AArch64` in the AArch64 document. Signed-off-by: Henry Wang <Henry.Wang@arm.com> 2020-06-12 00:58:50 +00:00			`cargo_args=("$@")`
			`[ $(uname -m) = "aarch64" ] && cargo_args+=("--no-default-features")`
scripts: Remove all references to 'mmio' feature Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2020-10-15 12:20:29 +00:00			`[ $(uname -m) = "aarch64" ] && cargo_args+=("--features kvm")`
ci: Pass target triple to the test scripts We pass it to the integration and unit tests script through --libc. Cargo tests are left unmodified. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2020-04-21 06:02:58 +00:00
ci: Simplify test scripts Since all unit and integration tests are run inside containers because they are called from dev_cli.sh, they always run as root. That's why both unit and integration scripts can be simplified as they don't need to apply specific capabilities and run cargo tests in a dedicated 'kvm' group. Fixes #1683 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2020-10-07 09:01:58 +00:00			`export RUST_BACKTRACE=1`
			`cargo test --target $BUILD_TARGET --workspace ${cargo_args[@]} \|\| exit 1;`