crosvm/integration_tests
Frederick Mayle 77e9606589 integration_tests: print more info on startup failure
I got stuck on the "/var/empty doesn't exist" error when setting up on a
new machine. This makes it much easier to diagnose.

Change-Id: I08f7e025fc3ddec92f58a0ce10c6a8ca6bdc84d7
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3939625
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Frederick Mayle <fmayle@google.com>
2022-10-10 20:25:18 +00:00
..
guest_under_test Update all copyright headers to match new style 2022-09-13 18:41:29 +00:00
tests integration_tests: print more info on startup failure 2022-10-10 20:25:18 +00:00
Cargo.toml prebuilts: move prebuilts tests under tests 2022-10-07 15:54:37 +00:00
README.md docs: Use mdformat to format markdown files 2022-01-27 21:29:11 +00:00
run Update all copyright headers to match new style 2022-09-13 18:41:29 +00:00

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.