ae5118f5c7
Run tests for sys_util_core, poll_token_derive and balloon_control on windows. Using dotfiles to disable/serialize test runs of a subset of crates does not work well with third party crates as it forces us to commit the dot file to the crate. The patch modifies and uses the script that runs linux tests. This patch also allows us to - build/test child crate even if parent crate has disabled build/test. - avoid building crosvm if it is not explicitly specified. RIP short lived .windows_build_test_skip. You allowed us to run noop kokoro tests. Test: py .\tools\impl\test_runner.py --arch x86_64 Bug: b:215610772 Change-Id: Icc6d04ffd7c0c33d4f60aeac16fc7d23881c387d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3459809 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com> |
||
---|---|---|
.. | ||
guest_under_test | ||
tests | ||
Cargo.toml | ||
README.md | ||
run |
Crosvm Integration 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
src/third_party/chromiumos-overlay/chromeos-base/crosvm/crosvm-9999.ebuild
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.