25724e2ccc
We need a file system that supports O_DIRECT. We know ext4 to work and tmpfs not to work. Try out O_DIRECT before running the individual tests. Follow up to changing the configuration so that the next time I can notice the failure reason faster. BUG=b:190435784 TEST=integration_tests/run Change-Id: I7f8a97005dd959a5d0af4d1a91459b7bffc0fa9b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3096427 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@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.