From: Dario Faggioli <dfaggioli@suse.com>
To: "alex.bennee@linaro.org" <alex.bennee@linaro.org>
Cc: Claudio Fontana <Claudio.Fontana@suse.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Problem running qos-test when building with gcc12 and LTO
Date: Wed, 25 May 2022 09:40:25 +0000 [thread overview]
Message-ID: <5bcb5ceb44dd830770d66330e27de6a4345fcb69.camel@suse.com> (raw)
In-Reply-To: <87v8tu5cyy.fsf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On Wed, 2022-05-25 at 07:41 +0100, Alex Bennée wrote:
> Dario Faggioli <dfaggioli@suse.com> writes:
> > I'll try to dig further. Any idea/suggestion anyone has, feel free.
> > :-)
>
> Sounds like there are still memory corruption/not initialised issues
> that are affected by moving things around.
>
Right. In fact, I've just tried to enable the tests (re)introduced by
8dcb404bff6d9147765d7dd3e9c8493372186420 one by one and:
- with only one of them enabled, whichever one it is, things seems fine
- with vhost_user_test_setup_reconnect and
vhost_user_test_setup_connect_fail enabled (in this order) things
fail
- with vhost_user_test_setup_connect_fail and
vhost_user_test_setup_flags_mismatch enabled (in this order) things
fail
- with vhost_user_test_setup_reconnect and
vhost_user_test_setup_flags_mismatch enabled (in this order) things
fail
Even if I keep vhost_user_test_setup_reconnect and
vhost_user_test_setup_connect_fail enabled, but change the order (i.e.,
I move the qos_add_test for connect-fail before the one for reconnect,
things also fail.
I haven't tried other combinations, so far...
> Does it still trigger errors with my latest virtio cleanup series
> (which
> adds more tests to qos-test):
>
> Subject: [PATCH v2 00/15] virtio-gpio and various virtio cleanups
> Date: Tue, 24 May 2022 16:40:41 +0100
> Message-Id: <20220524154056.2896913-1-alex.bennee@linaro.org>
>
I'll try it. I know it fails on master (at least two days ago's
master). I'll apply the series and re-test.
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-25 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 19:19 Problem running qos-test when building with gcc12 and LTO Dario Faggioli
2022-05-24 20:12 ` Dario Faggioli
2022-05-25 6:41 ` Alex Bennée
2022-05-25 9:40 ` Dario Faggioli [this message]
2022-05-25 11:30 ` Dario Faggioli
2022-05-25 13:49 ` Paolo Bonzini
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=5bcb5ceb44dd830770d66330e27de6a4345fcb69.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=Claudio.Fontana@suse.com \
--cc=alex.bennee@linaro.org \
--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 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).