bbd3bc3042
e2e_tests/run script was used as a convenience tool, and is superseded by tools/run_tests2. BUG=NONE TEST=tools/presubmit Change-Id: I52ea9d3718d005fd64506c6586624a07da66db85 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4705407 Commit-Queue: Ningyuan Wang <ningyuan@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
1.2 KiB
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_tests2 --dut=vm -E 'rdeps(e2e_tests)'
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.