From: Kevin Wolf <kwolf@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Hanna Reitz <hreitz@redhat.com>,
vsementsov@yandex-team.ru
Subject: Re: [PATCH 3/3] iotests/migrate-bitmaps-postcopy-test: drop the postcopy timing assertion
Date: Tue, 14 Jul 2026 13:28:19 +0200 [thread overview]
Message-ID: <alYdU5b2l9N-WZPe@redhat.com> (raw)
In-Reply-To: <20260710161309.1104712-4-den@openvz.org>
Am 10.07.2026 um 18:13 hat Denis V. Lunev geschrieben:
> test_postcopy_success asserted `downtime * 10 < postcopy_time` to
> confirm the run spent meaningful time in postcopy. This is an
> unnormalized wall-clock heuristic tuned to old hardware (commit
> e80a4150a5), and fails on fast hosts where the bitmap payload now
> transfers in under a second while switch-over downtime stays fixed
> (e.g. downtime=0.6s, postcopy_time=0.8s).
>
> It is also a weak proxy for the regression it guards against
> (postcopy degenerating to precopy): that is already covered by the
> bitmap sha256, mid-migration update and persistence checks, none of
> which depend on this timing.
>
> Drop the assertion; keep printing the timings under debug.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Hanna Reitz <hreitz@redhat.com>
I agree that this assertion failure doesn't mean that the test failed.
What it might mean is that maybe we didn't test the code as well as we
would have liked to.
Should we try to slow down/throttle the migration artificially to
trigger the cases we want to test here more reliably?
Kevin
> tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test b/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
> index c519e6db8c..f9c55b6395 100755
> --- a/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
> +++ b/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
> @@ -186,7 +186,6 @@ class TestDirtyBitmapPostcopyMigration(iotests.QMPTestCase):
> downtime = event_dist(event_stop, event_resume)
> postcopy_time = event_dist(event_resume, event_complete)
>
> - assert downtime * 10 < postcopy_time
> if debug:
> print('downtime:', downtime)
> print('postcopy_time:', postcopy_time)
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-07-14 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 16:13 [PATCH 0/3] iotests: fix three spurious local failures Denis V. Lunev
2026-07-10 16:13 ` [PATCH 1/3] iotests: run the test pool with the 'fork' start method Denis V. Lunev
2026-07-14 11:08 ` Kevin Wolf
2026-07-10 16:13 ` [PATCH 2/3] iotests: skip FUSE tests when FUSE is not usable Denis V. Lunev
2026-07-14 11:19 ` Kevin Wolf
2026-07-10 16:13 ` [PATCH 3/3] iotests/migrate-bitmaps-postcopy-test: drop the postcopy timing assertion Denis V. Lunev
2026-07-14 11:28 ` Kevin Wolf [this message]
2026-07-14 12:36 ` Vladimir Sementsov-Ogievskiy
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=alYdU5b2l9N-WZPe@redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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.