On Tue, Sep 27, 2022 at 06:09:22PM -0400, Michael S. Tsirkin wrote: > On Tue, Sep 27, 2022 at 11:44:56PM +0200, Paolo Bonzini wrote: > > I also second the idea of using avocado instead of pytest, by the way.
snip > Problem is I don't think avocado is yet at the level where I can > ask random developers to use it to check their ACPI patches. > > I just went ahead and rechecked and the situation isn't much better > yet. I think the focus of avocado is system testing of full guests with > KVM, not unit testing of ACPI. > > Let's start with installation on a clean box: ...snip... Do not do any of this stuff, it is irrelevant to QEMU's needs. A developer using Avocado with QEMU does nothing more than: make check-avocado The avocado framework itself is setup in a virtual env on first run by the makefile. Thus the developers don't need to install nor interact with avocado at all, merely write a test script and put it in tests/avocado/ in QEMU git. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|