02.02.2021 19:29, Vladimir Sementsov-Ogievskiy wrote:
02.02.2021 19:23, Kevin Wolf wrote:
Am 02.02.2021 um 17:13 hat Eric Blake geschrieben:
On 2/1/21 8:56 PM, Eric Blake wrote:
I had planned to send a pull request for this series today, but ran into
a snag. Without this series applied, './check -qcow2' fails 030, 185,
and 297.
297 appears to be fixed once Kevin's pull request lands (well, that may
be needing a v2). 185 appears to be just a whitespace difference that
missed fixing in 362ef77f9 and similar:
--- /home/eblake/qemu/tests/qemu-iotests/185.out
+++ 185.out.bad
@@ -89,7 +89,7 @@
'format': 'IMGFMT',
'sync': 'full',
'speed': 65536,
- 'x-perf': { 'max-chunk': 65536 } } }
+ 'x-perf': {'max-chunk': 65536} } }
030 is a bit tougher to figure out.
030 fail [09:40:32] [09:40:48] 16.9s (last: 15.4s) failed,
exit status 1
--- /home/eblake/qemu/tests/qemu-iotests/030.out
+++ 030.out.bad
@@ -1,5 +1,45 @@
-...........................
+WARNING:qemu.machine:qemu received signal 11; command:
So some qemu process segfaulted. Did you have a look at the resulting
coredump?
Kevin
Note that 30 is known to crash sometimes. Look at
"[PATCH RFC 0/5] Fix accidental crash in iotest 30"
https://patchew.org/QEMU/20201120161622.1537-1-vsement...@virtuozzo.com/
Also, I see that this series diverged with master.. Did you already rebased it?
If so, could you push it in your tree?
--
Best regards,
Vladimir
