On Wed, 2022-05-25 at 07:41 +0100, Alex Bennée wrote: > Dario Faggioli <dfaggi...@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.ben...@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)
signature.asc
Description: This is a digitally signed message part
