From: Dario Faggioli <dfaggioli@suse.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"cfontana@suse.de" <cfontana@suse.de>
Cc: "alex.bennee@linaro.org" <alex.bennee@linaro.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic
Date: Fri, 27 May 2022 07:26:27 +0000 [thread overview]
Message-ID: <94ef489c1721bdd741ba71c3fe75b3b66ec400b3.camel@suse.com> (raw)
In-Reply-To: <0e831d41-d338-ed6a-7530-a13d24675556@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Thu, 2022-05-26 at 20:18 +0200, Claudio Fontana wrote:
> Forget about his aspect, I think it is a separate problem.
>
> valgind of qos-test when run restricted to those specific paths (-p
> /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-net-pci/virtio-
> net/virtio-net-tests/vhost-user/reconnect for example)
> shows all clear,
>
> and still the test fails when run in a while loop after a few
> attempts:
>
Yes, this kind of matches what I've also seen and reported about in
<5bcb5ceb44dd830770d66330e27de6a4345fcb69.camel@suse.com>. If
enable/run just one of:
- reconnect
- flags_mismatch
- connect_fail
I see no issues.
As soon as two of those are run, one after the other, the problem
starts to appear.
However, Claudio, AFAIUI, you're seeing this with an older GCC and
without LTO, right?
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-27 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 18:06 make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic Claudio Fontana
2022-05-26 18:18 ` Claudio Fontana
2022-05-27 7:26 ` Dario Faggioli [this message]
2022-05-27 8:18 ` Claudio Fontana
2022-05-27 10:10 ` Claudio Fontana
2022-05-27 10:41 ` Dario Faggioli
2022-05-27 11:02 ` Alex Bennée
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=94ef489c1721bdd741ba71c3fe75b3b66ec400b3.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--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.