intermittent failures in iotest 108

Claudio Fontana posted 1 patch 1 year, 4 months ago
Failed in applying to current master (apply log)
intermittent failures in iotest 108
Posted by Claudio Fontana 1 year, 4 months ago
Hello Kevin and all,

I seem to be getting intermittent failures with mainline iotest 108. Is this already known?

../configure --enable-tcg --enable-kvm --enable-modules --enable-debug
make -j
make -j check


▶ 614/634 qcow2 108                                                                        FAIL          
614/634 qemu:block / qemu-iotests qcow2                                                    ERROR          155.16s   exit status 1
>>> MALLOC_PERTURB_=33 PYTHON=/usr/bin/python3 /usr/bin/sh /home/claudio/git/qemu/build-all/../tests/qemu-iotests/../check-block.sh qcow2
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
stderr:
--- /home/claudio/git/qemu/tests/qemu-iotests/108.out
+++ /home/claudio/git/qemu/build-all/tests/qemu-iotests/scratch/108.out.bad
@@ -152,40 +152,4 @@

 --- Rebuilding refcount structures on block devices ---

-{ "execute": "qmp_capabilities" }
-{"return": {}}
-{ "execute": "blockdev-create",
-       "arguments": {
-           "job-id": "create",
-           "options": {
-               "driver": "IMGFMT",
-               "file": "file",
-               "size": 67108864,
-               "cluster-size": 512
-           } } }
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "create"}}
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "create"}}
-{"return": {}}
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "waiting", "id": "create"}}
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "pending", "id": "create"}}
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "concluded", "id": "create"}}
-{ "execute": "job-dismiss", "arguments": { "id": "create" } }
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "create"}}
-{"return": {}}
-{ "execute": "quit" }
-{"return": {}}
-{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
-
-wrote 65536/65536 bytes at offset 0
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-
-ERROR cluster 0 refcount=0 reference=1
-Rebuilding refcount structure
-The following inconsistencies were found and repaired:
-
-    0 leaked clusters
-    1 corruptions
-
-Double checking the fixed image now...
-No errors were found on the image.
-*** done
+Timeout waiting for capabilities on handle 0

(test program exited with status code 1)
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

615/634 qemu:softfloat+softfloat-conv / fp-test-float-to-float                             OK              0.18s
616/634 qemu:softfloat+softfloat-conv / fp-test-int-to-float                               OK              0.18s
617/634 qemu:softfloat+softfloat-conv / fp-test-uint-to-float                              OK              0.17s
618/634 qemu:softfloat+softfloat-conv / fp-test-float-to-int                               OK              0.17s
619/634 qemu:softfloat+softfloat-conv / fp-test-float-to-uint                              OK              0.16s
620/634 qemu:softfloat+softfloat-conv / fp-test-round-to-integer                           OK              0.15s
621/634 qemu:softfloat+softfloat-compare / fp-test-lt_quiet                                OK              0.18s
622/634 qemu:softfloat+softfloat-compare / fp-test-le_quiet                                OK              0.19s
623/634 qemu:softfloat+softfloat-compare / fp-test-eq_signaling                            OK              0.24s
624/634 qemu:softfloat+softfloat-compare / fp-test-le                                      OK              0.24s
625/634 qemu:qapi-schema+qapi-doc / QAPI rST doc                                           OK              0.02s
626/634 qemu:softfloat+softfloat-ops / fp-test-sqrt                                        OK              0.15s
627/634 qemu:softfloat+softfloat-ops / fp-test-log2                                        OK              0.28s
628/634 qemu:qapi-schema+qapi-frontend / QAPI schema regression tests                      OK              0.33s
629/634 qemu:softfloat+softfloat-ops / fp-test-sub                                         OK              1.90s
630/634 qemu:softfloat+softfloat-ops / fp-test-add                                         OK              2.05s
631/634 qemu:decodetree / decodetree                                                       OK              2.57s
632/634 qemu:softfloat+softfloat-ops / fp-test-rem                                         OK              5.05s
633/634 qemu:softfloat+softfloat-ops / fp-test-div                                         OK              7.77s
634/634 qemu:softfloat+softfloat-ops / fp-test-mul                                         OK              9.03s

Summary of Failures:

614/634 qemu:block / qemu-iotests qcow2                                           ERROR          155.16s   exit status 1


Ok:                 567 
Expected Fail:      0 
Fail:               1   
Unexpected Pass:    0   
Skipped:            66  
Timeout:            0   



Re: intermittent failures in iotest 108
Posted by Kevin Wolf 1 year, 4 months ago
Am 07.11.2022 um 14:36 hat Claudio Fontana geschrieben:
> Hello Kevin and all,
> 
> I seem to be getting intermittent failures with mainline iotest 108. Is this already known?
> 
> ../configure --enable-tcg --enable-kvm --enable-modules --enable-debug
> make -j
> make -j check

At least I haven't hit it yet. Running just the one test case in a loop
doesn't seem to trigger it either. Maybe it only fails under load?

Kevin
Re: intermittent failures in iotest 108
Posted by Claudio Fontana 1 year, 4 months ago
On 11/10/22 14:50, Kevin Wolf wrote:
> Am 07.11.2022 um 14:36 hat Claudio Fontana geschrieben:
>> Hello Kevin and all,
>>
>> I seem to be getting intermittent failures with mainline iotest 108. Is this already known?
>>
>> ../configure --enable-tcg --enable-kvm --enable-modules --enable-debug
>> make -j
>> make -j check
> 
> At least I haven't hit it yet. Running just the one test case in a loop
> doesn't seem to trigger it either. Maybe it only fails under load?
> 
> Kevin
> 

I'll give it a few more spins, see how often I hit it.

Ciao,

C
Re: intermittent failures in iotest 108
Posted by Claudio Fontana 1 year, 4 months ago
On 11/10/22 14:51, Claudio Fontana wrote:
> On 11/10/22 14:50, Kevin Wolf wrote:
>> Am 07.11.2022 um 14:36 hat Claudio Fontana geschrieben:
>>> Hello Kevin and all,
>>>
>>> I seem to be getting intermittent failures with mainline iotest 108. Is this already known?
>>>
>>> ../configure --enable-tcg --enable-kvm --enable-modules --enable-debug
>>> make -j
>>> make -j check
>>
>> At least I haven't hit it yet. Running just the one test case in a loop
>> doesn't seem to trigger it either. Maybe it only fails under load?

btw are you running tests in parallel

make -j check

?