OpenE2K/qemu-e2k
13
4
Fork 0
Code Issues 4 Pull Requests Projects 2 Releases Activity

iotests/129: Limit backup's max-chunk/max-workers

Browse Source 
Right now, this does not change anything, because backup ignores
max-chunk and max-workers.  However, as soon as backup is switched over
to block-copy for the background copying process, we will need it to
keep 129 passing.

Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20210120102043.28346-1-mreitz@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
This commit is contained in:
Max Reitz 2021-01-20 11:20:43 +01:00
parent 55f3e5cb3b
commit 67a066fbe4
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
tests/qemu-iotests/129
View File

@ -71,9 +71,14 @@ class TestStopWithBlockJob(iotests.QMPTestCase):
sync="full", buf_size=65536)
def test_drive_backup(self):
# Limit max-chunk and max-workers so that block-copy will not
# launch so many workers working on so much data each that
# stop's bdrv_drain_all() would finish the job
self.do_test_stop("drive-backup", device="drive0",
target=self.target_img, format=iotests.imgfmt,
sync="full")
sync="full",
x_perf={ 'max-chunk': 65536,
'max-workers': 8 })
def test_block_commit(self):
# Add overlay above the source node so that we actually use a