From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
eblake@redhat.com, xiechanglong.d@gmail.com,
wencongyang2@huawei.com, hreitz@redhat.com, jsnow@redhat.com,
f.ebner@proxmox.com
Subject: Re: [PATCH v4 5/5] iotests: add backup-discard-source
Date: Tue, 11 Jun 2024 19:49:58 +0200 [thread overview]
Message-ID: <ZmiORpYFHEWUXQRI@redhat.com> (raw)
In-Reply-To: <20240313152822.626493-6-vsementsov@yandex-team.ru>
Am 13.03.2024 um 16:28 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Add test for a new backup option: discard-source.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
> Tested-by: Fiona Ebner <f.ebner@proxmox.com>
This test fails for me, and it already does so after this commit that
introduced it. I haven't checked what get_actual_size(), but I'm running
on XFS, so its preallocation could be causing this. We generally avoid
checking the number of allocated blocks in image files for this reason.
Kevin
backup-discard-source fail [19:45:49] [19:45:50] 0.8s failed, exit status 1
--- /home/kwolf/source/qemu/tests/qemu-iotests/tests/backup-discard-source.out
+++ /home/kwolf/source/qemu/build-clang/scratch/qcow2-file-backup-discard-source/backup-discard-source.out.bad
@@ -1,5 +1,14 @@
-..
+F.
+======================================================================
+FAIL: test_discard_cbw (__main__.TestBackup.test_discard_cbw)
+1. do backup(discard_source=True), which should inform
+----------------------------------------------------------------------
+Traceback (most recent call last):
+ File "/home/kwolf/source/qemu/tests/qemu-iotests/tests/backup-discard-source", line 147, in test_discard_cbw
+ self.assertLess(get_actual_size(self.vm, 'temp'), 512 * 1024)
+AssertionError: 1249280 not less than 524288
+
----------------------------------------------------------------------
Ran 2 tests
-OK
+FAILED (failures=1)
Failures: backup-discard-source
Failed 1 of 1 iotests
next prev parent reply other threads:[~2024-06-11 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 15:28 [PATCH v4 0/5] backup: discard-source parameter Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 1/5] block/copy-before-write: fix permission Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 2/5] block/copy-before-write: support unligned snapshot-discard Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 3/5] block/copy-before-write: create block_copy bitmap in filter node Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 4/5] qapi: blockdev-backup: add discard-source parameter Vladimir Sementsov-Ogievskiy
2024-03-13 16:08 ` Markus Armbruster
2024-03-14 13:44 ` Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 5/5] iotests: add backup-discard-source Vladimir Sementsov-Ogievskiy
2024-06-11 17:49 ` Kevin Wolf [this message]
2024-06-12 19:21 ` Vladimir Sementsov-Ogievskiy
2024-06-13 8:02 ` Kevin Wolf
2024-06-20 14:15 ` Vladimir Sementsov-Ogievskiy
2024-04-05 13:46 ` [PATCH v4 0/5] backup: discard-source parameter 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=ZmiORpYFHEWUXQRI@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.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 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.