From: Kevin Wolf <kwolf@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Martin Kletzander" <mkletzan@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-rust@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>,
werner@suse.de
Subject: Re: [PATCH 2/2] tests/qemu-iotests: Indent expected error messages
Date: Mon, 4 Aug 2025 13:33:53 +0200 [thread overview]
Message-ID: <aJCaoULvGgKjEL16@redhat.com> (raw)
In-Reply-To: <87v7n63lld.fsf@suse.de>
Am 01.08.2025 um 21:09 hat Fabiano Rosas geschrieben:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Fri, Aug 01, 2025 at 04:59:50PM +0200, Martin Kletzander wrote:
> >> From: Martin Kletzander <mkletzan@redhat.com>
> >>
> >> When running all tests the expected "killed" messages are indented
> >> differently than the actual ones, by three more spaces. Change it so
> >> that the messages match and tests pass.
> >
> > This would break the tests on my system and CI too.
> >
> > What distro are you seeing this on ?
> >
> > I'm guessing this is a different in either valgrind or C library ?
>
> It's bash, we have an open issue about it:
>
> https://gitlab.com/qemu-project/qemu/-/issues/3050
I see a patch has been posted to that bug, the most important part of
which is this added filtering:
--- a/tests/qemu-iotests/common.filter
+++ b/tests/qemu-iotests/common.filter 2025-07-25 11:39:22.419665788 +0000
@@ -75,7 +75,7 @@ _filter_qemu_io()
_filter_win32 | \
gsed -e "s/[0-9]* ops\; [0-9/:. sec]* ([0-9/.inf]* [EPTGMKiBbytes]*\/sec and [0-9/.inf]* ops\/sec)/X ops\; XX:XX:XX.X (XXX YYY\/sec and XXX ops\/sec)/" \
-e "s/: line [0-9][0-9]*: *[0-9][0-9]*\( Aborted\| Killed\)/:\1/" \
- -e "s/qemu-io> //g"
+ -e "s/qemu-io> //g" -e '/Killed/{ s/ \{2,\}/ /}'
}
# replace occurrences of QEMU_PROG with "qemu"
This approach makes sense to me, though I would have kept each sed
expression on a separate line.
And given that the context line above includes "Aborted" as well, maybe
have it here, too, though none of the actual test outputs have an
Aborted message any more since commit 3f39447. Or we could have a
cleanup patch first that removes the unused "Abort" above, just to keep
things consistent.
Either way, please post this as a proper patch on the mailing list.
Kevin
next prev parent reply other threads:[~2025-08-04 11:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 14:59 [PATCH 0/2] Few fixes I found when building QEMU with Rust Martin Kletzander
2025-08-01 14:59 ` [PATCH 1/2] rust: Add antoher variant for impl_vmstate_struct! macro Martin Kletzander
2025-08-01 21:44 ` Paolo Bonzini
2025-08-04 8:56 ` Martin Kletzander
2025-08-04 10:08 ` Paolo Bonzini
2025-08-04 12:04 ` Martin Kletzander
2025-08-04 13:06 ` Paolo Bonzini
2025-08-01 14:59 ` [PATCH 2/2] tests/qemu-iotests: Indent expected error messages Martin Kletzander
2025-08-01 15:48 ` Daniel P. Berrangé
2025-08-01 19:09 ` Fabiano Rosas
2025-08-04 8:20 ` Martin Kletzander
2025-08-04 11:33 ` Kevin Wolf [this message]
2025-08-06 6:54 ` Dr. Werner Fink
2025-08-11 9:05 ` Martin Kletzander
2025-08-12 15:35 ` Kevin Wolf
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=aJCaoULvGgKjEL16@redhat.com \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mkletzan@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=werner@suse.de \
/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).