mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-09 20:04:20 +00:00
Add a tool used in vsock tests to dev_container and guest rootfs BUG=b:254375643 TEST=`./tools/presubmit` with the new guest rootfs on the new dev_container Change-Id: I135e6d2d413bedffef0fd69edd4ab14080429e3a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3974349 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Takaya Saeki <takayas@chromium.org> Commit-Queue: Ryuichiro Chiba <chibar@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
# 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](http://go/crosvm/infra.md?cl=head#access-on-demand-to-upload-artifacts)
|
|
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.
|