From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 0/6] tests/functional: remove last use of avocado.utils
Date: Mon, 15 Sep 2025 11:24:41 +0100 [thread overview]
Message-ID: <87qzw8qahi.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250912182200.643909-1-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Fri, 12 Sep 2025 19:21:54 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> This simply imports the GDB code from avocado.utils to the QEMU
> functional test suite, and drops the other redundant avocado
> usage.
Missing patches include dropping the:
@skipIfMissingImports('avocado.utils')
from the reverse tests.
With this done can we remove the remaining references to avocado?
python/Makefile
110: @avocado --config avocado.cfg run tests/
118: @coverage run -m avocado --config avocado.cfg run tests/*.py
python/README.rst
73:- ``avocado.cfg`` Configuration for the Avocado test-runner.
python/qemu/machine/README.rst
5:QEMU. It is used by the iotests, vm tests, avocado tests, and several
python/qemu/utils/README.rst
5:debugging QEMU. It is used primarily by the vm and avocado tests.
python/setup.cfg
37: avocado-framework >= 90.0
python/tests/minreqs.txt
35:avocado-framework==90.0
python/tests/protocol.py
7:import avocado
160:class Smoke(avocado.Test):
208:class TestBase(avocado.Test):
>
> Daniel P. Berrangé (6):
> tests/functional: import GDB remote code from avocado
> tests/functional: convert reverse debug test to local gdb module
> tests/functional: replace avocado process with subprocess
> tests/functional: drop datadrainer class in reverse debugging
> tests/functional: close GDB socket in reverse debugging test
> tests/functional: use self.log for all logging
>
> tests/functional/aarch64/test_virt.py | 4 +-
> tests/functional/arm/test_integratorcp.py | 3 +-
> tests/functional/mips64el/test_malta.py | 3 +-
> tests/functional/qemu_test/gdb.py | 237 ++++++
> tests/functional/qemu_test/gdbmi_parser.py | 419 ++++++++++
> tests/functional/qemu_test/spark.py | 850 +++++++++++++++++++++
> tests/functional/replay_kernel.py | 16 +-
> tests/functional/reverse_debugging.py | 59 +-
> tests/functional/x86_64/test_acpi_bits.py | 31 +-
> 9 files changed, 1557 insertions(+), 65 deletions(-)
> create mode 100644 tests/functional/qemu_test/gdb.py
> create mode 100644 tests/functional/qemu_test/gdbmi_parser.py
> create mode 100644 tests/functional/qemu_test/spark.py
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-09-15 10:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 18:21 [PATCH 0/6] tests/functional: remove last use of avocado.utils Daniel P. Berrangé
2025-09-12 18:21 ` [PATCH 1/6] tests/functional: import GDB remote code from avocado Daniel P. Berrangé
2025-09-15 10:06 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 2/6] tests/functional: convert reverse debug test to local gdb module Daniel P. Berrangé
2025-09-15 10:06 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 3/6] tests/functional: replace avocado process with subprocess Daniel P. Berrangé
2025-09-15 10:07 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 4/6] tests/functional: drop datadrainer class in reverse debugging Daniel P. Berrangé
2025-09-15 10:18 ` Alex Bennée
2025-09-15 10:38 ` Daniel P. Berrangé
2025-09-15 12:04 ` Alex Bennée
2025-09-15 12:05 ` Alex Bennée
2025-09-12 18:21 ` [PATCH 5/6] tests/functional: close GDB socket in reverse debugging test Daniel P. Berrangé
2025-09-15 10:18 ` Alex Bennée
2025-09-12 18:22 ` [PATCH 6/6] tests/functional: use self.log for all logging Daniel P. Berrangé
2025-09-15 10:19 ` Alex Bennée
2025-09-15 10:39 ` Daniel P. Berrangé
2025-09-15 10:24 ` Alex Bennée [this message]
2025-09-15 10:42 ` [PATCH 0/6] tests/functional: remove last use of avocado.utils Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87qzw8qahi.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.