mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-28 17:44:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/run_tests

95 lines
3.1 KiB
Text
Raw Normal View History

Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
#!/usr/bin/env python3
# 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.
#
# Runs tests for crosvm.
#
Kokoro: Extensive polishing and bugfixing This CL fixes some of the issues that prevented the test system from running on other workstations. - Builders run by Kokoro will not use a scratch mount. It's not needed, and will cause issues if stored on /tmp with noexec set. - Running podman with label=disable to prevent selinux issues. The run_tests implementation has been moved to a separate file and updated with parsing of cargo test output. This allows simpler test output and integration with the test results UI in sponge. The sponge test UI can make it much easier to see which tests failed, and to find the log of that test case. This CL also includes an ./ci/kokoro/uprev script to uprev the manifest versions. And runs the uprev. BUG=b:174861002 TEST=Tested by forcing a kokoro build with this CL Change-Id: I0cba9bb68915e2558a4ea6061dd9ba0a7050421b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2669712 Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-02-02 23:18:10 +00:00
# See `ci/README.md` or `./run_tests -h` for more details.
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
Kokoro: Extensive polishing and bugfixing This CL fixes some of the issues that prevented the test system from running on other workstations. - Builders run by Kokoro will not use a scratch mount. It's not needed, and will cause issues if stored on /tmp with noexec set. - Running podman with label=disable to prevent selinux issues. The run_tests implementation has been moved to a separate file and updated with parsing of cargo test output. This allows simpler test output and integration with the test results UI in sponge. The sponge test UI can make it much easier to see which tests failed, and to find the log of that test case. This CL also includes an ./ci/kokoro/uprev script to uprev the manifest versions. And runs the uprev. BUG=b:174861002 TEST=Tested by forcing a kokoro build with this CL Change-Id: I0cba9bb68915e2558a4ea6061dd9ba0a7050421b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2669712 Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-02-02 23:18:10 +00:00
from typing import List, Dict
from ci.test_runner import Requirements, main
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
# A list of all crates and their requirements
Fix io_uring tests for running on Kokoro Some of the multi-threaded tests had race conditions that show up when running inside the Kokoro Test VMs. To wake up and complete all running threads, no-ops are inserted into the uring. However, each thread can grab a list of results. On the test VMs, all no-ops are read by one thread, leaving the others running, blocking the test from completing. Since this is just a test.. let's just leave the threads hanging and let the OS take care of them. BUG=b:181673923 TEST=./test_all Change-Id: I504b6db9cf934e2454d27c1155667b4b0f7fbc77 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2750783 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-03-11 00:39:46 +00:00
# See ci/test_runner.py for documentation on the requirements
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
CRATE_REQUIREMENTS: Dict[str, List[Requirements]] = {
"aarch64": [Requirements.AARCH64],
"acpi_tables": [],
"arch": [],
"assertions": [],
"base": [],
"bit_field": [],
"bit_field_derive": [],
Integrate p9 and cros-fuzz into crosvm build Updates path and includes the libraries in the test runner. BUG=b:193243281,b:191509642 TEST=./run_tests passes and executes the new tests Change-Id: If38126fa6bdf2a0a3dca5a79c6e4d76857617fd0 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3049671 Tested-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
2021-07-23 17:06:40 +00:00
"common/cros-fuzz": [Requirements.SEPARATE_WORKSPACE],
"common/p9": [Requirements.SEPARATE_WORKSPACE, Requirements.X86_64],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"cros_async": [Requirements.DISABLED],
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
"crosvm": [Requirements.DO_NOT_RUN],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"crosvm_plugin": [Requirements.X86_64],
"data_model": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"devices": [
Requirements.SINGLE_THREADED,
Requirements.PRIVILEGED,
Requirements.X86_64,
],
disk: composite: switch tests to tempfile Use tempfile rather than SharedMemory for temporary files in the composite disk unit tests. This fixes an API incompatibility that was missed because these tests are only enabled with the composite-disk feature. This also enables the disk tests in test_all with the privileged option so that they run in the VM; this allows the memfd_create syscall used in the async_read/write tests to work. BUG=b:181674168 TEST=cargo test -p disk --features=composite-disk TEST=./test_all Change-Id: I869b5daa29904b3558440e7b650713e8e5085d81 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2743401 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
2021-03-09 00:39:31 +00:00
"disk": [Requirements.PRIVILEGED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"enumn": [],
"fuse": [],
"fuzz": [Requirements.DISABLED],
"gpu_display": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"hypervisor": [Requirements.PRIVILEGED, Requirements.X86_64],
Enable integration_tests on Kokoro for X86 Increases the communication timeout to 10 secs since we are running twice nested KVMs, and things get a bit slower. BUG=b:181675114 TEST=./test_all Change-Id: Ifa3ea05952cd8a4f7fbe4fefb12143098243c21a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2752341 Tested-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2021-03-11 20:40:42 +00:00
"integration_tests": [Requirements.PRIVILEGED, Requirements.X86_64],
Fix io_uring tests for running on Kokoro Some of the multi-threaded tests had race conditions that show up when running inside the Kokoro Test VMs. To wake up and complete all running threads, no-ops are inserted into the uring. However, each thread can grab a list of results. On the test VMs, all no-ops are read by one thread, leaving the others running, blocking the test from completing. Since this is just a test.. let's just leave the threads hanging and let the OS take care of them. BUG=b:181673923 TEST=./test_all Change-Id: I504b6db9cf934e2454d27c1155667b4b0f7fbc77 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2750783 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-03-11 00:39:46 +00:00
"io_uring": [
Requirements.SEPARATE_WORKSPACE,
Requirements.PRIVILEGED,
Requirements.SINGLE_THREADED,
],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"kernel_cmdline": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"kernel_loader": [Requirements.PRIVILEGED],
"kvm_sys": [Requirements.PRIVILEGED],
"kvm": [Requirements.PRIVILEGED, Requirements.X86_64],
Add FFI library providing control socket access This allows other languages to communicate directly with the control socket without having to invoke `crosvm` BUG=None TEST=Ran ./run_tests Change-Id: Icbf5905c41643b080bae3613b73a032467db1c4c Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2772798 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Kevin Hamacher <hamacher@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2021-03-18 11:41:23 +00:00
"libcrosvm_control": [],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"linux_input_sys": [],
"net_sys": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"net_util": [Requirements.PRIVILEGED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"power_monitor": [],
"protos": [],
"qcow_utils": [],
"resources": [],
run_tests: enable rutabaga_gfx and vm_memory tests Add the privileged requirement so that these tests run in a VM and can successfully call memfd_create(). BUG=b:181672913 BUG=b:181675101 TEST=./test_all Change-Id: Ic0eadade4e625e50e73682771a9c6fbb92468af2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2754487 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
2021-03-11 21:25:19 +00:00
"rutabaga_gfx": [Requirements.CROS_BUILD, Requirements.PRIVILEGED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"sync": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"sys_util": [Requirements.SINGLE_THREADED, Requirements.PRIVILEGED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"poll_token_derive": [],
"tempfile": [],
"tpm2-sys": [],
"tpm2": [],
"usb_sys": [],
"usb_util": [],
"vfio_sys": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"vhost": [Requirements.PRIVILEGED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"virtio_sys": [],
"vm_control": [],
run_tests: enable rutabaga_gfx and vm_memory tests Add the privileged requirement so that these tests run in a VM and can successfully call memfd_create(). BUG=b:181672913 BUG=b:181675101 TEST=./test_all Change-Id: Ic0eadade4e625e50e73682771a9c6fbb92468af2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2754487 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
2021-03-11 21:25:19 +00:00
"vm_memory": [Requirements.PRIVILEGED],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"x86_64": [Requirements.X86_64, Requirements.PRIVILEGED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
}
# Just like for crates, lists requirements for each cargo feature flag.
FEATURE_REQUIREMENTS: Dict[str, List[Requirements]] = {
Integrate audio_streams into crosvm, add stub libcras implementation The `# ignored by ebuild` tag will remove the path to libcras_stub and allows crosvm to be built with the actual libcras implementation. This allows all other platforms to build without depending on `third_party/adhd/cras/client/libcras`, which is a prerequisite for externalizing crosvm. An empty libcras_stub crate is provided to keep cargo happy in external builds. To build with cargo against libcras, the setup_cros_cargo.sh script can be used. BUG=b:191511078 TEST=Tests in crosvm and cros_sdk both pass: $ ./test_all $ cros_run_unit_tests --package=crosvm Cq-Depend: chromium:2993483 Change-Id: I86aad23a86c78e580c1724fb311f870b25d6b09e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2988154 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org>
2021-06-23 18:34:31 +00:00
"chromeos": [Requirements.DISABLED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"audio": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"gpu": [Requirements.CROS_BUILD],
"plugin": [Requirements.PRIVILEGED, Requirements.X86_64],
Switch to submodules based workflow Instead of requiring crosvm to be checked out via the chromeos manifest to access dependencies in the ChromeOS monorepo, this change adds git submodules to third_party/. The CI scripts and Cargo.toml are updated to use the new paths. BUG=b:194336213 TEST=git clone --recursive https://chromium.googlesource.com/chromiumos/platform/crosvm cd crosvm cargo test ./test_all ./ci/kokoro/simulate_all Change-Id: I9859d18176e21909ac3a140976fbd67cc14129bb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3049003 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
2021-07-23 20:22:39 +00:00
"power-monitor-powerd": [Requirements.DISABLED],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"tpm": [Requirements.CROS_BUILD],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"video-decoder": [Requirements.DISABLED],
"video-encoder": [Requirements.DISABLED],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"wl-dmabuf": [Requirements.DISABLED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"x": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"virgl_renderer_next": [Requirements.CROS_BUILD],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"composite-disk": [],
Add VM to builders The VM allows both the x86 and aarch64 builders to run tests which require access to kernel devices that docker would prevent us from accessing. The VM is automatically started in the endpoint script, and the environment is set up to execute `cargo test` binaries inside the VM. This allows for convenient interactive usage. The VM is also integrated into the run_tests scripts, executing tests that do not require special privileges first, while the VM is still booting up, then execuing the remaining tests in the VM. BUG=b:177228167,b:177951276 TEST=These test calls pass: ./ci/builder --vm ./run_tests ./ci/aarch64_builder --vm ./run_tests ./run_tests Change-Id: I20bf2cd848e944d411b97f1f8356279e312d8583 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2642766 Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2021-01-21 19:06:44 +00:00
"virgl_renderer": [Requirements.CROS_BUILD],
"gfxstream": [Requirements.DISABLED],
Test Runner for crosvm The ./run_tests script will select which tests to run on the host. Unfortunately a lot of our tests require dependencies or access to certain kernel devices. We cannot run all tests on all hosts. The test runner works with the CI builders: To run all x86 tests: ./ci/builder ./run_tests --all To run tests on aarch64: ./ci/aarch64_builder ./run_tests --all Or to just run tests that can be run on a standard debian buster system without obscure chromeos dependencies: ./run_tests Eventually, the test runner should run tests via the VM of the aarch64_builder, currently only those tests that can be run with user-space emulation are executed. Currently some tests remain disabled in the runner, as they do not pass in the CI builders yet. These will be enabled as the builders are set up to allow for them to be run. BUG=b:173833661 TEST=Ran the above commands. Change-Id: Id69027793348f4d3f20adf5333d8bdfff1aa9c8b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2633889 Tested-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-01-14 21:10:31 +00:00
"gdb": [],
}
Kokoro: Extensive polishing and bugfixing This CL fixes some of the issues that prevented the test system from running on other workstations. - Builders run by Kokoro will not use a scratch mount. It's not needed, and will cause issues if stored on /tmp with noexec set. - Running podman with label=disable to prevent selinux issues. The run_tests implementation has been moved to a separate file and updated with parsing of cargo test output. This allows simpler test output and integration with the test results UI in sponge. The sponge test UI can make it much easier to see which tests failed, and to find the log of that test case. This CL also includes an ./ci/kokoro/uprev script to uprev the manifest versions. And runs the uprev. BUG=b:174861002 TEST=Tested by forcing a kokoro build with this CL Change-Id: I0cba9bb68915e2558a4ea6061dd9ba0a7050421b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2669712 Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2021-02-02 23:18:10 +00:00
main(CRATE_REQUIREMENTS, FEATURE_REQUIREMENTS)
Reference in a new issue Copy permalink