From: John Snow <jsnow@redhat.com>
To: "Cleber Rosa" <crosa@redhat.com>, "Alex Bennée" <alex.bennee@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: acceptance-system-fedora failures
Date: Tue, 6 Oct 2020 19:07:24 -0400 [thread overview]
Message-ID: <f9e09f0b-3915-382c-d670-8d33d164ad7b@redhat.com> (raw)
I'm seeing this gitlab test fail quite often in my Python work; I don't
*think* this has anything to do with my patches, but maybe I need to try
and bisect this more aggressively.
The very first hint of an error I see is on line 154:
https://gitlab.com/jsnow/qemu/-/jobs/776334918#L154
22:05:36 ERROR|
22:05:36 ERROR| Reproduced traceback from:
/builds/jsnow/qemu/build/tests/venv/lib64/python3.8/site-packages/avocado/core/test.py:753
22:05:36 ERROR| Traceback (most recent call last):
22:05:36 ERROR| File
"/builds/jsnow/qemu/build/tests/acceptance/avocado_qemu/__init__.py",
line 171, in setUp
22:05:36 ERROR| self.cancel("No QEMU binary defined or found in the
build tree")
Is this a known problem?
--js
next reply other threads:[~2020-10-06 23:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 23:07 John Snow [this message]
2020-10-07 5:20 ` acceptance-system-fedora failures Philippe Mathieu-Daudé
2020-10-07 7:13 ` Philippe Mathieu-Daudé
2020-10-07 8:23 ` Thomas Huth
2020-10-07 8:51 ` Pavel Dovgalyuk
2020-10-07 9:57 ` Philippe Mathieu-Daudé
2020-10-07 11:22 ` Alex Bennée
2020-10-07 12:20 ` Pavel Dovgalyuk
2020-10-07 12:49 ` Philippe Mathieu-Daudé
2020-10-07 13:11 ` Pavel Dovgalyuk
2020-10-08 10:26 ` Philippe Mathieu-Daudé
2020-10-08 11:50 ` Kevin Wolf
2020-10-09 10:37 ` Pavel Dovgalyuk
2020-10-13 8:57 ` Philippe Mathieu-Daudé
2020-10-07 12:17 ` Pavel Dovgalyuk
2020-10-07 14:03 ` John Snow
2020-10-07 7:23 ` Thomas Huth
2020-10-07 8:19 ` Philippe Mathieu-Daudé
2020-10-07 14:38 ` Cleber Rosa
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=f9e09f0b-3915-382c-d670-8d33d164ad7b@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=qemu-devel@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 NNTP newsgroup(s).