From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] tests/functional: skip vulkan test if mssing vulkaninfo
Date: Thu, 13 Mar 2025 08:17:45 +0100 [thread overview]
Message-ID: <0dfd507a-290d-4354-aee0-9da031b3449a@redhat.com> (raw)
In-Reply-To: <e554655e-7f28-4d45-8faa-3c06b72f74ad@redhat.com>
On 13/03/2025 08.13, Thomas Huth wrote:
>
> Missing "i" in "mssing" in the subject.
>
> On 12/03/2025 20.03, Alex Bennée wrote:
>> I could have sworn I had this is a previous iteration of the patches
>> but I guess it got lost in a re-base. As we are going to call
>> vulkaninfo to probe for "bad" drivers we need to skip if the binary
>> isn't available.
>>
>> Fixes: 9f7e493d11 (tests/functional: skip vulkan tests with nVidia)
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> tests/functional/test_aarch64_virt_gpu.py | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tests/functional/test_aarch64_virt_gpu.py b/tests/functional/
>> test_aarch64_virt_gpu.py
>> index f19a47f8b6..314d994a7a 100755
>> --- a/tests/functional/test_aarch64_virt_gpu.py
>> +++ b/tests/functional/test_aarch64_virt_gpu.py
>> @@ -115,6 +115,7 @@ def test_aarch64_virt_with_virgl_blobs_gpu(self):
>> self._run_virt_weston_test("glmark2-wayland -b:duration=1.0")
>> @skipIfMissingCommands('zstd')
>> + @skipIfMissingCommands('vulkaninfo')
>> def test_aarch64_virt_with_vulkan_gpu(self):
>
> The check_output call in this function is already wrapped with a try-except
> statement, isn't that enough already?
Hmm, looks like a missing vulkaninfo is giving some other kind of exception,
so we need this patch indeed. I'll queue it for my pull request today.
Thomas
prev parent reply other threads:[~2025-03-13 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 19:03 [RFC PATCH] tests/functional: skip vulkan test if mssing vulkaninfo Alex Bennée
2025-03-13 7:13 ` Thomas Huth
2025-03-13 7:17 ` Thomas Huth [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=0dfd507a-290d-4354-aee0-9da031b3449a@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.