Hi all,
Another quick update on recent infra and project health updates for upstream crosvm.
Important update upfront: We are updating our revert policy to revert downstream, fix upstream. Please avoid reverting changes in upstream crosvm.
Thank you!
New ./tools/cl to upload changes to the main crosvm repository, replacing repo upload.
New baremetal example for running an x86_64 application in crosvm (Thank you romanton)
More tests enabled on windows builds: vhost, vmm_vhost, hypervisor, vm_memory and many more (Thank you B* upstreamers)
The video feature can now be used (and tested) without ChromeOS vda. (Thank you acourbot)
Large refactoring of command line arguments to use argh (Thank you romanton)
Crosvm Luci is making good progress and almost at parity with Kokoro. We expect to make the switch early Q3.
Luci is already running the push_to_github and merge_with_chromeos processes.
The ChromeOS merge bot follows a new process: go/crosvm-merge-improvements
Crosvm Infra added a crosvm-on-chromeos post-submit builder to catch downstream issues early on.
An updated roadmap of upcoming infra projects and changes:
Switch all development to the new repository
Migrate all crosvm resources (test images, containers) to crosvm-infra.
Serve documentation on crosvm.dev
Tangentially related to crosvm upstream. ChromeOS’ crostini tests provide the most complete test coverage of crosvm on linux, but are very unreliable
Investigate and document sources of unreliability and stabilize the tests.
The goal is to have all code living in crosvm built and tested in crosvm infra.
Collect and report test coverage metrics
Untested features in upstream have a plan to add coverage
The ChromeOS build team is working on building crosvm with bazel in ChromeOS.
Upstream crosvm will switch to be built with bazel as well.
Both cargo and bazel will be supported until all downstream projects are migrated.