From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Willian Rampazzo <willianr@redhat.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH] tests/acceptance: Add a 'virt_kvm' test using the GICv3
Date: Tue, 06 Apr 2021 18:12:21 +0100 [thread overview]
Message-ID: <87ft03wd3w.fsf@linaro.org> (raw)
In-Reply-To: <7a720701-a34f-ccf4-d116-a0f0703b5f83@redhat.com>
Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> On 3/31/21 5:45 PM, Alex Bennée wrote:
>>
>> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
>>
>>> The current 'virt_kvm' test is restricted to GICv2, but can also
>>> work with a GICv3. Duplicate it but add a GICv3 test which can be
>>> tested on some hardware.
>>>
>>> Noticed while running:
>>>
>>> $ avocado --show=app run -t machine:virt tests/acceptance/
>>> ...
>>> (2/6) tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_kvm: ERROR: Unexpected empty reply from server (1.82 s)
>>>
>>> The job.log content is:
>>>
>>> L0351 DEBUG| Output: 'qemu-system-aarch64: host does not support in-kernel GICv2 emulation\n'
>>>
>>> With this patch:
>>>
>>> $ avocado --show=app run -t device:gicv3 tests/acceptance/
>>> (1/1)
>>> tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_kvm_gicv3:
>>> PASS (55.10 s)
>>
>> On the new aarch64 machine which is GICv3 I get the following:
>>
>> (006/142) tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_kvm_gicv2: ERROR: Unexpected empty reply from server (0.47 s)
>>
>> which it shouldn't have run. However:
>>
>> ./tests/venv/bin/avocado --show=app run -t device:gic3 tests/acceptance/
>> Test Suite could not be create. No test references provided nor any other arguments resolved into tests
>>
>> Is this something that has regressed or am I doing it wrong?
>
> Typo in the tag: "device:gic3" -> "device:gicv3"
Doh!
But what about:
/tests/venv/bin/avocado run tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_kvm_gicv2
JOB ID : 396696d8f9d31d970878cb46025b2ced76f3623f
JOB LOG : /home/alex/avocado/job-results/job-2021-04-06T17.11-396696d/job.log
(1/1) tests/acceptance/boot_linux.py:BootLinuxAarch64.test_virt_kvm_gicv2: ERROR: Unexpected empty reply from server (0.65 s)
RESULTS : PASS 0 | ERROR 1 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB TIME : 0.96 s
why doesn't that skip?
--
Alex Bennée
next prev parent reply other threads:[~2021-04-06 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 22:48 [PATCH] tests/acceptance: Add a 'virt_kvm' test using the GICv3 Philippe Mathieu-Daudé
2020-09-30 13:24 ` Willian Rampazzo
2020-10-05 8:08 ` Philippe Mathieu-Daudé
2021-03-31 15:45 ` Alex Bennée
2021-04-06 15:22 ` Philippe Mathieu-Daudé
2021-04-06 17:12 ` Alex Bennée [this message]
2021-04-12 17:55 ` Philippe Mathieu-Daudé
2021-04-13 16:25 ` Philippe Mathieu-Daudé
2021-04-13 16:32 ` Alex Bennée
2021-05-26 18:04 ` 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=87ft03wd3w.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
--cc=willianr@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).