qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
	qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Gustavo Romero" <gustavo.romero@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] tests/functional: add --debug CLI arg
Date: Wed, 16 Jul 2025 09:23:19 -0700	[thread overview]
Message-ID: <ad2026f8-0907-4bde-83c3-b52b71e848a6@linaro.org> (raw)
In-Reply-To: <20250716-functional_tests_debug_arg-v1-1-6a9cd68318bb@linaro.org>

On 7/15/25 11:08 PM, Manos Pitsidianakis wrote:
> Add argument parsing to functional tests to improve developer experience
> when running individual tests. All logs are printed to stdout
> interspersed with TAP output.
> 
>    ./pyvenv/bin/python3 ../tests/functional/test_aarch64_virt.py --help
>    usage: test_aarch64_virt [-h] [-d]
> 
>    QEMU Functional test
> 
>    options:
>      -h, --help   show this help message and exit
>      -d, --debug  Also print test and console logs on stdout. This will
>                   make the TAP output invalid and is meant for debugging
>                   only.
> 
> Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
> ---
>   docs/devel/testing/functional.rst      |  2 ++
>   tests/functional/qemu_test/testcase.py | 51 ++++++++++++++++++++++++++++++++--
>   2 files changed, 50 insertions(+), 3 deletions(-)

Thanks, that's a great idea, and more convenient than the poor man's 
tail -f I was using for that.

Tested-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>


  reply	other threads:[~2025-07-16 16:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  6:08 [PATCH] tests/functional: add --debug CLI arg Manos Pitsidianakis
2025-07-16 16:23 ` Pierrick Bouvier [this message]
2025-07-17  8:42 ` Alex Bennée
2025-07-17  8:46   ` Thomas Huth
2025-07-17 10:36     ` Alex Bennée
2025-07-21  7:25       ` Thomas Huth
2025-07-17  8:47   ` Manos Pitsidianakis
2025-07-17 10:04     ` Alex Bennée
2025-07-17 10:13       ` Manos Pitsidianakis
2025-07-21 20:38   ` John Snow
2025-07-24 19:47     ` Thomas Huth
2025-08-07 21:46       ` John Snow
2025-09-09 10:37         ` Thomas Huth
2025-09-15 19:54           ` John Snow
2025-09-19  6:13             ` Thomas Huth
2025-07-17  9:21 ` Daniel P. Berrangé
2025-07-17  9:27   ` Manos Pitsidianakis
2025-07-17  9:39     ` Daniel P. Berrangé
2025-07-17 10:02       ` Manos Pitsidianakis

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=ad2026f8-0907-4bde-83c3-b52b71e848a6@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=gustavo.romero@linaro.org \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=philmd@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).