From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>,
"P. Berrange, Daniel" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Mathieu-Daudé, Philippe" <f4bug@amsat.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Bonzini, Paolo" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH v1 6/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test
Date: Wed, 17 Feb 2021 17:20:28 +0400 [thread overview]
Message-ID: <CAMxuvaw09S68CmqoeXo2HcBEJE7=ni7iMXjVaMOAX9gWNQ+AKg@mail.gmail.com> (raw)
In-Reply-To: <20210217121932.19986-7-alex.bennee@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Wed, Feb 17, 2021 at 4:19 PM Alex Bennée <alex.bennee@linaro.org> wrote:
> This is a band-aid with a TODO for cases when QEMU doesn't start due
> to missing VirGL. Longer term we could do with some proper feature
> probing.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
---
> tests/acceptance/virtio-gpu.py | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/tests/acceptance/virtio-gpu.py
> b/tests/acceptance/virtio-gpu.py
> index ab1a4c1a71..ab18cddbb7 100644
> --- a/tests/acceptance/virtio-gpu.py
> +++ b/tests/acceptance/virtio-gpu.py
> @@ -85,7 +85,12 @@ def test_virtio_vga_virgl(self):
> "-append",
> kernel_command_line,
> )
> - self.vm.launch()
> + try:
> + self.vm.launch()
> + except:
> + # TODO: probably fails because we are missing the VirGL
> features
> + self.cancel("VirGL not enabled?")
> +
> self.wait_for_console_pattern("as init process")
> exec_command_and_wait_for_pattern(
> self, "/usr/sbin/modprobe virtio_gpu", ""
> --
> 2.20.1
>
>
[-- Attachment #2: Type: text/html, Size: 2139 bytes --]
next prev parent reply other threads:[~2021-02-17 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 12:19 [PATCH v1 0/6] my current testing/next queue (meson/gitlab/fedora bump) Alex Bennée
2021-02-17 12:19 ` [PATCH v1 1/6] meson.build: expose TCG cross compiler information in summary Alex Bennée
2021-02-17 12:19 ` [PATCH v1 2/6] gitlab-ci: Display Avocado log content when tests timeout Alex Bennée
2021-02-17 13:38 ` Thomas Huth
2021-02-17 12:19 ` [PATCH v1 3/6] gitlab-ci.yml: Run check-tcg with TCI Alex Bennée
2021-02-17 16:38 ` Philippe Mathieu-Daudé
2021-02-17 17:51 ` Richard Henderson
2021-02-17 12:19 ` [PATCH v1 4/6] docker: Bump Fedora images to release 33 Alex Bennée
2021-02-17 12:19 ` [PATCH v1 5/6] travis.yml: Limit simultaneous jobs to 3 Alex Bennée
2021-02-17 12:19 ` [PATCH v1 6/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test Alex Bennée
2021-02-17 13:20 ` Marc-André Lureau [this message]
2021-02-19 15:53 ` Willian Rampazzo
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='CAMxuvaw09S68CmqoeXo2HcBEJE7=ni7iMXjVaMOAX9gWNQ+AKg@mail.gmail.com' \
--to=marcandre.lureau@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).