1ae4e549e5
In working towards enabling unit tests, import the correct arch defines for riscv64 where needed. TEST=from dev container run: ``` cargo nextest run --workspace --no-default-features \ --exclude tpm2 \ --exclude tpm2-sys \ --exclude libvda \ --exclude libva \ --exclude ffmpeg \ --exclude vmm_vhost \ --exclude system_api \ --exclude gpu_display \ --color=always \ --no-run \ --target riscv64gc-unknown-linux-gnu ``` Change-Id: Ia7853de8ee0a11a5fdb716546a146f892229b0cb Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4501091 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com> |
||
---|---|---|
.. | ||
benches | ||
fixture | ||
guest_under_test | ||
tests | ||
Cargo.toml | ||
README.md | ||
run |
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.
Running with locally built kernel/rootfs
If the test needs to run offline, or 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.
The use_local_build.sh script does this for you:
$ source guest_under_test/use_local_build.sh
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. Never try to modify an existing prebuilt as the new images may break
tests in older versions.