From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Cornelia Huck <cohuck@redhat.com>,
"open list:S390 general arch..." <qemu-s390x@nongnu.org>,
Cleber Rosa <crosa@redhat.com>, Beraldo Leal <bleal@redhat.com>,
Jan Richter <jarichte@redhat.com>
Subject: Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing
Date: Wed, 16 Nov 2022 12:12:24 +0100 [thread overview]
Message-ID: <2575d09e-f7a7-a8fc-2a70-d8e7d56353c2@linaro.org> (raw)
In-Reply-To: <4b6e726c-55aa-cc44-7c95-1f31655ff37a@redhat.com>
On 16/11/22 11:58, Thomas Huth wrote:
> On 16/11/2022 11.23, Philippe Mathieu-Daudé wrote:
>> Cc'ing Jan/Cleber/Beraldo.
>>
>> On 16/11/22 10:43, Thomas Huth wrote:
>>> On 15/11/2022 12.13, Philippe Mathieu-Daudé wrote:
>>>> On 15/11/22 12:05, Thomas Huth wrote:
>>>>> On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote:
>>>>>> Hi,
>>>>>>
>>>>>> As of v7.2.0-rc0 I am getting:
>>>>>>
>>>>>> (101/198)
>>>>>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (23.51 s)
>>>>>
>>>>> Is it 100% reproducible? ... the test is known to be a little bit
>>>>> shaky, that's also why it is disabled in the gitlab CI.
>>>>
>>>> I am running it on my workstation, not GitLab.
>>>
>>> I just double-checked and for me, it's working fine an my laptop,
>>> with both, rc0 and rc1.
>>>
>>>> 5/5 failures. I'll skip it locally (no need to send a patch) and we can
>>>> have a look after the release.
>>>
>>> If it is a real bug, we should fix it before the release. Could you
>>> maybe bisect it, please?
>>>
>>> Also, what do you get when dumping the console? I.e.:
>>>
>>> ./tests/venv/bin/avocado --show=console run -t arch:s390x \
>>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora
>>
>> When running with the current (old) Avocado runner I get:
>>
>> Avocado crashed: TypeError: cannot pickle '_thread.RLock' object
>> Please include the traceback info and command line used on your bug
>> report
>> Report bugs visiting
>> https://github.com/avocado-framework/avocado/issues/new
>>
>> I can use the 'new' runner:
>>
>> $ TMPDIR=/tmp ./tests/venv/bin/avocado --show=app,console run
>> --test-runner=nrunner -t arch:s390x
>
> Uh, don't do that. nrunner does not seem to be able to execute that test
> yet. Or did you also upgrade your avocado to a newer installation? ...
> in that case it sounds like you might have messed up your installation?
> Maybe try again with a fresh and clean checkout of the QEMU repository /
> a new build folder.
Well the current (old) runner doesn't work on Darwin ARM64:
Avocado crashed: TypeError: cannot pickle '_thread.RLock' object
Using `TMPDIR=/tmp avocado --test-runner=nrunner` almost all other tests
pass. I'll wait for Cleber's nrunner update before re-testing/bisecting.
prev parent reply other threads:[~2022-11-16 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 11:03 tests/avocado/machine_s390_ccw_virtio: Fedora test failing Philippe Mathieu-Daudé
2022-11-15 11:05 ` Thomas Huth
2022-11-15 11:13 ` Philippe Mathieu-Daudé
2022-11-16 9:43 ` Thomas Huth
2022-11-16 10:23 ` Philippe Mathieu-Daudé
2022-11-16 10:58 ` Thomas Huth
2022-11-16 11:12 ` Philippe Mathieu-Daudé [this message]
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=2575d09e-f7a7-a8fc-2a70-d8e7d56353c2@linaro.org \
--to=philmd@linaro.org \
--cc=bleal@redhat.com \
--cc=cohuck@redhat.com \
--cc=crosa@redhat.com \
--cc=jarichte@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@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).