commit | 47e25297d524ae7c869c0dfb6c4206478ba782f0 | [log] [tgz] |
---|---|---|
author | Dennis Kempin <denniskempin@google.com> | Fri Jun 03 18:01:11 2022 +0000 |
committer | Dennis Kempin <denniskempin@google.com> | Fri Jun 03 19:12:04 2022 +0000 |
tree | 2530e178ad2f0d761c3ef558a1fe9dd37c2d7ae5 | |
parent | ca66addad0f4448a8b8607e119f8ffc2a39c57e4 [diff] |
merge_bot: Handle merge conflicts The bot cannot resolve those automatically. To ease the process, we will upload the merge anyway, so the oncall can download and resolve the conflict. Dry runs are not created when there are conflicts, they are bound to fail and there is nothing the oncall can do about conflicts until the actual merge is generated. BUG=b:234847583 TEST=MERGE_BOT_TEST=1 ./tools/chromeos/merge_bot update-merges / update-dry-runs Change-Id: I409e6b99284ff8a98b504b390c35329875d6a8b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3689544 Reviewed-by: Anton Romanov <romanton@google.com> Tested-by: kokoro <noreply+kokoro@google.com>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the Chrome OS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on Chrome OS devices.