From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: Re: qos-test is annoyingly noisy
Date: Mon, 28 Jul 2025 16:39:02 +0200 [thread overview]
Message-ID: <87ms8omlbt.fsf@pond.sub.org> (raw)
In-Reply-To: <ed3009be-8707-4340-a8ee-2523f77fe861@redhat.com> (Paolo Bonzini's message of "Wed, 23 Jul 2025 18:38:45 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 7/23/25 16:28, Markus Armbruster wrote:
>> Noise starting with "stdout: " has been polluting output of "make check"
>> for a while. I traced it to qos-test. Output of "make
>> check-qtest-aarch64" appended as an example.
>> Blessed silence if I revert commit 30ea13e9d97d (tests/qtest: use
>> qos_printf instead of g_test_message).
>> Alex, what shall we do here?
>
> What is printing "stdout:", is it glib? I think glib should be using g_test_message() to do those "stdout:" prints.
I doubt it's glib. When I run the test directly, like
$ QTEST_QEMU_BINARY=./qemu-system-aarch64 QTEST_QEMU_IMG=./qemu-img time /work/armbru/qemu/bld/tests/qtest/qos-test
I see the offending lines without "stdout:"
# Start of vhost-user tests
qemu-system-aarch64: Failed to set msg fds.
qemu-system-aarch64: vhost VQ 0 ring restore failed: -22: Invalid argument (22)
qemu-system-aarch64: Failed to set msg fds.
qemu-system-aarch64: vhost VQ 1 ring restore failed: -22: Invalid argument (22)
# # qos_test running single test in subprocess
# # set_protocol_features: 0x42
# # set_owner: start of session
# # vhost-user: un-handled message: 14
# # vhost-user: un-handled message: 14
# # set_vring(0)=enabled
# # set_vring(1)=enabled
# # set_vring(0)=enabled
# # set_vring(1)=enabled
# # set_vring(0)=enabled
# # set_vring(1)=enabled
# # set_vring(0)=enabled
# # set_vring(1)=enabled
# # set_vring(0)=enabled
# # set_vring(1)=enabled
# # set_vring_num: 0/256
# # set_vring_addr: 0x7f7fcc000000/0x7f7fcbfff000/0x7f7fcc001000
# # set_vring_num: 1/256
ok 28 /aarch64/virt/generic-pcihost/pci-bus-generic/pci-bus/virtio-net-pci/virtio-net/virtio-net-tests/vhost-user/migrate
I believe the prefix "stdout: <number>: UNKNOWN: " comes from the test
harness.
> But I agree a more practical alternative is a revert.
I'll post one.
next prev parent reply other threads:[~2025-07-28 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 14:28 qos-test is annoyingly noisy Markus Armbruster
2025-07-23 16:38 ` Paolo Bonzini
2025-07-28 14:39 ` Markus Armbruster [this message]
2025-07-28 14:57 ` 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=87ms8omlbt.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.