On 28/09/2022 09.06, Daniel P. Berrangé wrote:
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
Right. And if you want to run individual tests, you can also do it like this:
make check-venv # Only for the first time
./tests/venv/bin/avocado run tests/avocado/boot_linux.py
Or run tests via tags (very convenient for maintainers):
./tests/venv/bin/avocado run -t arch:s390x tests/avocado/
HTH,
Thomas