On Tue, Jan 17, 2023 at 11:16:32AM +0000, Peter Maydell wrote: > On Tue, 17 Jan 2023 at 10:44, Daniel P. Berrangé <berra...@redhat.com> wrote: > > Something random that looks like bad text data > > > > ▶ 166/619 /ptimer/oneshot > > policy=no_immediate_����������������������������������������������������������������...snip....������������� > > I don't understand this one. The string comes from > tests/unit/ptimer-test.c:add_ptimer_tests() but that > code creates the test string using g_strlcat() and > g_strdup_printf(), so I don't see how it could end > up being junk, especially not at that point in > the string. I guess it's possible something else in > the test is managing to corrupt the g_test test name > strings?
Actually it looks like something else spewing ���������� a to stderr, and this getting intermixed with stdout from the test suite. The test case name isn't corrupt, as I see the remaining "reload,..." bit that jouins with 'policy=no_immediate_" Wonder what's responsible for this garbage on stderr... With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
