qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] qemu-iotests RC0+ status


From: John Snow
Subject: [Qemu-devel] qemu-iotests RC0+ status
Date: Thu, 12 Jul 2018 18:16:05 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

Hi, on Fedora 28 x64 host, as of 68f1b569 I'm seeing:

`./check -v -qcow`
        - occasional stall on 052
        - stalls on 216

`./check -v -qed`
        - stalls on 200

`./check -v -luks`
        - failures on 226.


052 is something I can't reproduce. The test takes quite a while, so
maybe at some points I am simply not being patient enough.


216 appears to have never worked for qcow1.


226 is my fault: the test doesn't handle LUKS well, because it sets
TEST_IMG to something sneaky:
'driver=luks,key-secret=keysec0,file.filename=/path/to/src/qemu/bin/git/tests/qemu-iotests/scratch/t.luks'
... my test expected this to be a real file and doesn't suffer this
particularly well. I've sent a patch.


200 appears to regress on this commit:
f45280cbf66d8e58224f6a253d0ae2aa72cc6280 is the first bad commit
commit f45280cbf66d8e58224f6a253d0ae2aa72cc6280
Author: Greg Kurz <address@hidden>
Date:   Mon May 28 14:03:59 2018 +0200



Thanks,
--js



reply via email to

[Prev in Thread] Current Thread [Next in Thread]