qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Jiang Jiacheng <jiangjiacheng@huawei.com>,
	Leonardo Bras <leobras@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 3/3] tests/qtest: Re-enable multifd cancel test
Date: Tue, 9 Jan 2024 10:12:58 +0800	[thread overview]
Message-ID: <ZZyrqnk3nJ3WIX8v@x1n> (raw)
In-Reply-To: <87frz73nr7.fsf@suse.de>

On Mon, Jan 08, 2024 at 11:26:04AM -0300, Fabiano Rosas wrote:
> Peter Xu <peterx@redhat.com> writes:
> 
> > On Wed, Jun 07, 2023 at 10:27:15AM +0200, Juan Quintela wrote:
> >> Fabiano Rosas <farosas@suse.de> wrote:
> >> > We've found the source of flakiness in this test, so re-enable it.
> >> >
> >> > Signed-off-by: Fabiano Rosas <farosas@suse.de>
> >> > ---
> >> >  tests/qtest/migration-test.c | 10 ++--------
> >> >  1 file changed, 2 insertions(+), 8 deletions(-)
> >> >
> >> > diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
> >> > index b0c355bbd9..800ad23b75 100644
> >> > --- a/tests/qtest/migration-test.c
> >> > +++ b/tests/qtest/migration-test.c
> >> > @@ -2778,14 +2778,8 @@ int main(int argc, char **argv)
> >> >      }
> >> >      qtest_add_func("/migration/multifd/tcp/plain/none",
> >> >                     test_multifd_tcp_none);
> >> > -    /*
> >> > -     * This test is flaky and sometimes fails in CI and otherwise:
> >> > -     * don't run unless user opts in via environment variable.
> >> > -     */
> >> > -    if (getenv("QEMU_TEST_FLAKY_TESTS")) {
> >> > -        qtest_add_func("/migration/multifd/tcp/plain/cancel",
> >> > -                       test_multifd_tcp_cancel);
> >> > -    }
> >> > +    qtest_add_func("/migration/multifd/tcp/plain/cancel",
> >> > +                   test_multifd_tcp_cancel);
> >> >      qtest_add_func("/migration/multifd/tcp/plain/zlib",
> >> >                     test_multifd_tcp_zlib);
> >> >  #ifdef CONFIG_ZSTD
> >> 
> >> Reviewed-by: Juan Quintela <quintela@redhat.com>
> >> 
> >> 
> >> There was another failure with migration test that I will post during
> >> the rest of the day.  It needs both to get it right.
> >
> > This one didn't yet land upstream.  I'm not sure, but maybe Juan was saying
> > about this change:
> >
> >         commit d2026ee117147893f8d80f060cede6d872ecbd7f
> >         Author: Juan Quintela <quintela@trasno.org>
> >         Date:   Wed Apr 26 12:20:36 2023 +0200
> >
> >         multifd: Fix the number of channels ready
> 
> That's not it. It was something in the test itself around the fact that
> we use two sets of: from/to. There was supposed to be a situation where
> we'd start 'to2' while 'to' was still running and that would cause
> issues (possibly with sockets).
> 
> I think what might have happened is that someone merged a fix through
> another tree and Juan didn't notice. I think this is the one:
> 
>   commit f2d063e61ee2026700ab44bef967f663e976bec8
>   Author: Xuzhou Cheng <xuzhou.cheng@windriver.com>
>   Date:   Fri Oct 28 12:57:32 2022 +0800
>   
>       tests/qtest: migration-test: Make sure QEMU process "to" exited after migration is canceled
>       
>       Make sure QEMU process "to" exited before launching another target
>       for migration in the test_multifd_tcp_cancel case.
>       
>       Signed-off-by: Xuzhou Cheng <xuzhou.cheng@windriver.com>
>       Signed-off-by: Bin Meng <bin.meng@windriver.com>
>       Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>       Message-Id: <20221028045736.679903-8-bin.meng@windriver.com>
>       Signed-off-by: Thomas Huth <thuth@redhat.com>

Hmm, i see.

> 
> > Fabiano, did you try to reproduce multifd-cancel with current master?  I'm
> > wondering whether this test has already been completely fixed, then maybe
> > we can pick up this patch now.
> 
> Yes, let's merge it. I have kept it enabled during testing of all of the
> recent race conditions we've debugged and haven't seen it fail. Current
> master also looks fine.

It needs a trivial touchup, but then I queued it.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2024-01-09  2:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 14:45 [PATCH 0/3] migration: Fix multifd cancel test Fabiano Rosas
2023-06-06 14:45 ` [PATCH 1/3] migration/multifd: Rename threadinfo.c functions Fabiano Rosas
2023-06-06 18:38   ` Peter Xu
2023-06-06 19:34     ` Fabiano Rosas
2023-06-06 20:03       ` Peter Xu
2023-06-07  6:30   ` Juan Quintela
2023-06-07  7:56   ` Philippe Mathieu-Daudé
2023-06-06 14:45 ` [PATCH 2/3] migration/multifd: Protect accesses to migration_threads Fabiano Rosas
2023-06-06 18:43   ` Peter Xu
2023-06-07  8:26   ` Juan Quintela
2023-06-07 12:00     ` Fabiano Rosas
2023-06-07 13:25       ` Peter Xu
2023-06-07 16:58         ` Juan Quintela
2023-06-06 14:45 ` [PATCH 3/3] tests/qtest: Re-enable multifd cancel test Fabiano Rosas
2023-06-07  8:27   ` Juan Quintela
2024-01-08  6:42     ` Peter Xu
2024-01-08 14:26       ` Fabiano Rosas
2024-01-09  2:12         ` Peter Xu [this message]
2024-01-09  7:21           ` Thomas Huth
2024-01-09  7:48             ` Peter Xu
2024-01-09  8:44               ` Thomas Huth

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=ZZyrqnk3nJ3WIX8v@x1n \
    --to=peterx@redhat.com \
    --cc=farosas@suse.de \
    --cc=jiangjiacheng@huawei.com \
    --cc=leobras@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).