From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, thuth@redhat.com, quintela@redhat.com
Subject: Re: [PATCH] tests/migration: Tweek auto converge limits check
Date: Mon, 6 Mar 2023 15:39:01 +0000 [thread overview]
Message-ID: <ZAYJFZq71nIRy6V3@redhat.com> (raw)
In-Reply-To: <20230306152612.52291-1-dgilbert@redhat.com>
On Mon, Mar 06, 2023 at 03:26:12PM +0000, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Thomas found an autoconverge test failure where the
> migration completed before the autoconverge had kicked in.
>
> To try and avoid this again:
> a) Reduce the usleep in test_migrate_auto_converge
> so that it should exit quicker when autoconverge kicks in
> b) Make the loop exit immediately rather than have the sleep
> when it does start autoconverge, otherwise the autoconverge
> might succeed during the sleep.
> c) Reduce inc_pct so auto converge happens more slowly
> d) Reduce the max-bandwidth in migrate_ensure_non_converge
> to make the ensure more ensure.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> tests/qtest/migration-test.c | 19 +++++++++++--------
> 1 file changed, 11 insertions(+), 8 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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 :|
prev parent reply other threads:[~2023-03-06 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:26 [PATCH] tests/migration: Tweek auto converge limits check Dr. David Alan Gilbert (git)
2023-03-06 15:39 ` Daniel P. Berrangé [this message]
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=ZAYJFZq71nIRy6V3@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).