qemu-s390x
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing


From: Thomas Huth
Subject: Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing
Date: Wed, 16 Nov 2022 11:58:47 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0

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.

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]