crosvm/integration_tests/run

#!/bin/bash
# Copyright 2021 The Chromium OS Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file

# We require the crosvm binary to build before running the integration tests.
# There is an RFC for cargo to allow for this kind of dependency:
# https://github.com/rust-lang/cargo/issues/9096
cd $(dirname $0)
(cd .. && cargo build $@)
cargo test $@
Run integration_tests by calling crosvm binary Instead of instanciating crosvm directly, we can start the binary as a sub-process. This includes parsing of crosvm options in the tests, and makes the test cases closer to real-world usage. To make make this possible, we need to make sure that the crosvm binary is uploaded to the VM before running the test, which is done by the sync_so script, which is baked into the builder container. We prevent future container re-builds for just maintaining the script, I have removed them from the container, and call the scripts from the local source directly. The test runner is also updated to ensure all package binaries are built (currently only tests are built). BUG=b:182841358 TEST=./test_all passes Change-Id: I7dfd21abcb2b90fe125eb43f85572fbf645b888a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2744280 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> 2021-02-22 22:40:08 +00:00			`#!/bin/bash`
			`# Copyright 2021 The Chromium OS Authors. All rights reserved.`
			`# Use of this source code is governed by a BSD-style license that can be`
			`# found in the LICENSE file`

			`# We require the crosvm binary to build before running the integration tests.`
			`# There is an RFC for cargo to allow for this kind of dependency:`
			`# https://github.com/rust-lang/cargo/issues/9096`
			`cd $(dirname $0)`
			`(cd .. && cargo build $@)`
			`cargo test $@`