qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/2] tests/functional: collect more info in base.log file
Date: Tue, 28 Oct 2025 18:26:49 +0000	[thread overview]
Message-ID: <20251028182651.873256-1-berrange@redhat.com> (raw)

This came about from looking at info in

https://gitlab.com/qemu-project/qemu/-/jobs/11877115717

where it appears we've hung in a QMP 'quit' command

https://gitlab.com/qemu-project/qemu/-/jobs/11877115717/artifacts/external_file/build/tests/functional/ppc64/test_pseries.pseriesMachine.test_ppc64_linux_big_boot/base.log

but don't have conclusive proof since we're not capturing
logs for qemu.qmp.

Daniel P. Berrangé (2):
  tests/functional: include logger name and function in messages
  tests/functional: include the lower level QMP log messages

 tests/functional/qemu_test/testcase.py | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.51.1



             reply	other threads:[~2025-10-28 18:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 18:26 Daniel P. Berrangé [this message]
2025-10-28 18:26 ` [PATCH 1/2] tests/functional: include logger name and function in messages Daniel P. Berrangé
2025-10-29  7:06   ` Thomas Huth
2025-10-28 18:26 ` [PATCH 2/2] tests/functional: include the lower level QMP log messages Daniel P. Berrangé
2025-10-29  7:12   ` Thomas Huth
2025-10-29  8:12     ` Daniel P. Berrangé
2025-10-29  8:30       ` Thomas Huth
2025-10-29  9:00         ` 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=20251028182651.873256-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@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).