On Tue, Mar 10, 2020 at 10:54 AM, Ard Biesheuvel wrote:<br />
<blockquote>This means we can reasonably require any contributor not to regress on<br />those platforms, given how they have full access to it, and this is<br />actually where i would like us to take the next step when it comes to<br />ci automation, i.e., automatically flag PRs that break the boot on a<br />selected set of qemu based configs.</blockquote>
I appreciate the viewpoint but I don't think edk2 has "required" this yet and I would push back on that if it was brought up for community discussion.&nbsp; As you know I believe contributing to edk2 is much too hard already, and filled with custom edk2 workflows, and this one would only make it more of a burden to contribute.&nbsp;&nbsp;<br /><br />I do however agree that if this is important to the edk2 community, systems/automation should be setup to run this type of thing.&nbsp; If that happens, i don't think it is much harder to do it for multi-repo than single repo and if done right for multi-repo then other platforms can opt in as well and the efforts to build this infrastructure will scale well beyond a single virtual platform.<br /><br />Thanks<br />Sean