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

tests/iotests: be a little more forgiving on the size test

Browse Source 
At least on ZFS this was failing as 512 was less than or equal to 512.
I suspect the reason is additional compression done by ZFS and however
qemu-img gets the actual size.

Loosen the criteria to make sure after is not bigger than before and
also dump the values in the report.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Robert Foley <robert.foley@linaro.org>
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20200225124710.14152-9-alex.bennee@linaro.org>
This commit is contained in:
Alex Bennée 2020-02-25 20:20:09 +00:00
parent c9331e9c28
commit 002375895c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
tests/qemu-iotests/214
View File

@ -125,9 +125,9 @@ $QEMU_IO -c "write -P 0xcc $offset $data_size" "json:{\
sizeB=$($QEMU_IMG info --output=json "$TEST_IMG" | sizeB=$($QEMU_IMG info --output=json "$TEST_IMG" |
sed -n '/"actual-size":/ s/[^0-9]//gp') sed -n '/"actual-size":/ s/[^0-9]//gp')
if [ $sizeA -le $sizeB ] if [ $sizeA -lt $sizeB ]
then then
echo "Compression ERROR" echo "Compression ERROR ($sizeA < $sizeB)"
fi fi
$QEMU_IMG check --output=json "$TEST_IMG" | $QEMU_IMG check --output=json "$TEST_IMG" |