From: Christian Borntraeger <borntraeger@de.ibm.com>
To: qemu block <qemu-block@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: qemu io test: spurious failures of 030
Date: Thu, 10 Jun 2021 09:54:04 +0200 [thread overview]
Message-ID: <e40bf8ee-8a20-1251-911e-ceba6f1cee05@de.ibm.com> (raw)
Folks,
I have CI on s390 on qemu/master for each commit. And from time to time I do get spurious failures of 030. (always 030 and nothing else).
I have a hard time reproducing this manually so I cannot debug this at the moment. Has anyone seen this as well?
030 ... [09:34:06] ... 030 fail [09:34:06] [09:34:09] 3.2s failed, exit status 1
--- tests/qemu-iotests/030.out
+++ 030.out.bad
@@ -1,5 +1,45 @@
-...........................
+.............WARNING:qemu.machine.machine:qemu received signal 11; command: "build/tests/qemu-iotests/../../qemu-system-s390x -display none -vga none -chardev socket,id=mon,path=/tmp/tmpt3vg8hqd/qemu-2816608-monitor.sock -mon chardev=mon,mode=control -qtest unix:path=/tmp/tmpt3vg8hqd/qemu-2816608-qtest.sock -accel qtest -nodefaults -display none -accel qtest -drive if=virtio,id=drive0,file=/tmp/devel-iotests-9771/img-8.img,format=qcow2,cache=writeback,aio=threads,backing.backing.backing.backing.backing.backing.backing.backing.node-name=node0,backing.backing.backing.backing.backing.backing.backing.node-name=node1,backing.backing.backing.backing.backing.backing.node-name=node2,backing.backing.backing.backing.backing.node-name=node3,backing.backing.backing.backing.node-name=node4,backing.backing.backing.node-name=node5,backing.backing.node-name=node6,backing.node-name=node7,node-name=node8"
+EE.............
+======================================================================
+ERROR: test_stream_parallel (__main__.TestParallelOps)
+----------------------------------------------------------------------
+Traceback (most recent call last):
+ File "tests/qemu-iotests/030", line 260, in test_stream_parallel
+ for event in self.vm.get_qmp_events(wait=True):
+ File "tests/qemu-iotests/../../python/qemu/machine/machine.py", line 597, in get_qmp_events
+ events = self._qmp.get_events(wait=wait)
+ File "tests/qemu-iotests/../../python/qemu/qmp/__init__.py", line 338, in get_events
+ self.__get_events(wait)
+ File "tests/qemu-iotests/../../python/qemu/qmp/__init__.py", line 207, in __get_events
+ raise QMPConnectError("Error while reading from socket")
+qemu.qmp.QMPConnectError: Error while reading from socket
+
+======================================================================
+ERROR: test_stream_parallel (__main__.TestParallelOps)
+----------------------------------------------------------------------
+Traceback (most recent call last):
+ File "tests/qemu-iotests/../../python/qemu/machine/machine.py", line 489, in _do_shutdown
+ self._soft_shutdown(timeout, has_quit)
+ File "tests/qemu-iotests/../../python/qemu/machine/machine.py", line 469, in _soft_shutdown
+ self._qmp.cmd('quit')
+ File "tests/qemu-iotests/../../python/qemu/qmp/__init__.py", line 288, in cmd
+ return self.cmd_obj(qmp_cmd)
+ File "tests/qemu-iotests/../../python/qemu/qmp/__init__.py", line 266, in cmd_obj
+ self.__sock.sendall(json.dumps(qmp_cmd).encode('utf-8'))
+BrokenPipeError: [Errno 32] Broken pipe
+
+The above exception was the direct cause of the following exception:
+
+Traceback (most recent call last):
+ File "tests/qemu-iotests/030", line 227, in tearDown
+ self.vm.shutdown()
+ File "tests/qemu-iotests/../../python/qemu/machine/machine.py", line 519, in shutdown
+ self._do_shutdown(timeout, has_quit)
+ File "tests/qemu-iotests/../../python/qemu/machine/machine.py", line 492, in _do_shutdown
+ raise AbnormalShutdown("Could not perform graceful shutdown") \
+qemu.machine.machine.AbnormalShutdown: Could not perform graceful shutdown
+
----------------------------------------------------------------------
Ran 27 tests
-OK
+FAILED (errors=2)
next reply other threads:[~2021-06-10 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 7:54 Christian Borntraeger [this message]
2021-06-10 12:50 ` qemu io test: spurious failures of 030 Vladimir Sementsov-Ogievskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e40bf8ee-8a20-1251-911e-ceba6f1cee05@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).