cloud-hypervisor/scripts/run_unit_tests.sh

#!/bin/bash

source $HOME/.cargo/env

cargo test --workspace --no-run
pushd target/debug
ls  | grep net_util | grep -v "\.d" | xargs -n 1 sudo setcap cap_net_admin,cap_net_raw+ep
popd

sudo adduser $USER kvm
newgrp kvm << EOF || exit 1
  export RUST_BACKTRACE=1
  cargo test --workspace "$@" || exit 1;
EOF
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`

tests: Use the workspace to unit test all the crates Make all the crates members of the workspace so that "cargo test --workspace" will find them all and test them with the features enabled that we use. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2020-01-02 18:40:37 +00:00			`cargo test --workspace --no-run`
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			`pushd target/debug`
build: Ensure caps needed for unit test are set In some situations it is possible for the setting of the capabilities to fail due to the variable naming of the build artifacts resulting in the first parameter to setcap being rejected and thus the whole command failing. Use xargs -n 1 to ensure that every potential target independently has its caps set. Further it was observed that in some situations the binary produced by cargo test --all --no-run would not be used and instead a new binary would be produced when the test was run using the second method. This again would result in test failures as that binary did not have the desired capabilities set. Therefore build the test binaries with the same methodology used to run them. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-07-19 07:57:20 +00:00			`ls \| grep net_util \| grep -v "\.d" \| xargs -n 1 sudo setcap cap_net_admin,cap_net_raw+ep`
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			`popd`

tests: Use newgrp to run unit tests Rather than set filesystem permissions on the /dev/kvm device instead use the kvm group added by installing qemu for running the unit tests. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-08-16 14:11:47 +00:00			`sudo adduser $USER kvm`
			`newgrp kvm << EOF \|\| exit 1`
tests: Make panics generate a backtrace This will help pinpoint issues when debugging test failures. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-08-16 15:08:16 +00:00			`export RUST_BACKTRACE=1`
scripts: dev_cli: Pass unit and integration test args to cargo test In order, among other things, to use the development CLI to run specific integration tests. For example, to run only the memory_overhead integration test: ./scripts/dev_cli.sh tests --integration -- memory_overhead Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2020-02-04 13:49:21 +00:00			`cargo test --workspace "$@" \|\| exit 1;`
tests: Use newgrp to run unit tests Rather than set filesystem permissions on the /dev/kvm device instead use the kvm group added by installing qemu for running the unit tests. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-08-16 14:11:47 +00:00			`EOF`