qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: John Snow <jsnow@redhat.com>, Cleber Rosa <crosa@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: acceptance-system-fedora failures
Date: Wed, 7 Oct 2020 07:20:49 +0200	[thread overview]
Message-ID: <4e191372-c332-8f69-85e2-1ff6ead0f40d@redhat.com> (raw)
In-Reply-To: <f9e09f0b-3915-382c-d670-8d33d164ad7b@redhat.com>

On 10/7/20 1:07 AM, John Snow wrote:
> 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")

Last year the Avocado developers said we could have a clearer
log error report, but meanwhile this verbose output is better
that not having anything ¯\_(ツ)_/¯

> 
> Is this a known problem?

"No QEMU binary defined or found in the build tree" is not a
problem, it means a test is skipped because the qemu-system-$ARCH
binary is not found. In your case this is because your job
(acceptance-system-fedora) is based on build-system-fedora
which only build the following targets:

    TARGETS: tricore-softmmu microblaze-softmmu mips-softmmu
      xtensa-softmmu m68k-softmmu riscv32-softmmu ppc-softmmu
      sparc64-softmmu

Now I don't understand what binary the EmptyCPUModel/Migration tests
are expecting. Maybe these tests only work when a single target is
built? IOW not expecting that the python code searching for a binary
return multiple ones? -> Eduardo/Cleber.

w.r.t. the error in your build, I told Thomas about the
test_ppc_mac99/day15/invaders.elf timeouting but he said this is
not his area. Richard has been looking yesterday to see if it is
a TCG regression, and said the test either finished/crashed raising
SIGCHLD, but Avocado parent is still waiting for a timeout, so the
children become zombie and the test hang.

Not sure that helps :)

Regards,

Phil.



  reply	other threads:[~2020-10-07  5:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 23:07 acceptance-system-fedora failures John Snow
2020-10-07  5:20 ` Philippe Mathieu-Daudé [this message]
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=4e191372-c332-8f69-85e2-1ff6ead0f40d@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    /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).