4cba337895
The process only works with cargo test. Not with run_tests. BUG=b:301351266 TEST=None Change-Id: Iaf20c01e32746d263dab297b2f13adea568e1b98 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5123311 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> |
||
---|---|---|
.. | ||
benches | ||
fixture | ||
guest_under_test | ||
tests | ||
Cargo.toml | ||
README.md |
Crosvm End to End Tests
These tests run a crosvm VM on the host to verify end to end behavior. They use a prebuilt guest kernel and rootfs, which is downloaded from google cloud storage.
The e2e_tests can be executed by:
$ ./tools/run_tests --dut=vm -E 'rdeps(e2e_tests)'
Running with locally built kernel/rootfs
If you want to make changes to the kernel or rootfs, you have to specify the environment variables
CROSVM_CARGO_TEST_KERNEL_BINARY
and CROSVM_CARGO_TEST_ROOTFS_IMAGE
to point to the right files
and then run cargo test
.
The use_local_build.sh script does this for you:
$ source guest_under_test/use_local_build.sh
$ cargo test
Note: The custom images cannot be used with tools/run_tests
.
Uploading prebuilts
Note: Only Googlers with access to the crosvm-testing cloud storage bin can upload prebuilts.
To upload the modified rootfs, you will have to uprev the PREBUILT_VERSION
variable in:
./guest_under_test/PREBUILT_VERSION
and request a permission
to become a member of the crosvm-policy-uploader
group.
Then run the upload script to build and upload the new prebuilts.
# Install QEMU-user-static to build aarch64 images
$ sudo apt install binfmt-support qemu-user-static
# Register binfmt_misc entries
$ docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
# Build and upload the new artifacts
$ ./guest_under_test/upload_prebuilts.sh
Never try to modify an existing prebuilt as the new images may break tests in older versions.