From: Cleber Rosa <crosa@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Auger Eric" <eric.auger@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [PATCH for 6.1 0/6] virtio-gpu acceptance test: use current device name
Date: Wed, 14 Jul 2021 13:40:45 -0400 [thread overview]
Message-ID: <20210714174051.28164-1-crosa@redhat.com> (raw)
The virtio-gpu acceptance tests are currently broken because of a
mismatch in the device option and name (see patch 5).
The exact failure is:
qemu-system-x86_64: -device virtio-vga,virgl=on: Property 'virtio-vga.virgl' not found
While at it, I've included a few cleanups and improvements to the very
same test file.
A pipeline can be seen here (applied top of my python-next):
https://gitlab.com/cleber.gnu/qemu/-/pipelines/337000139
I've also applied it on top of current master (4aa2454d9) and verified
the fix.
If all patches are considered too much for the soft freeze, I can
re-send patch 5 by itself.
Cleber Rosa (6):
tests/acceptance/virtio-gpu.py: use require_accelerator()
tests/acceptance/virtio-gpu.py: combine x86_64 arch tags
tests/acceptance/virtio-gpu.py: combine CPU tags
tests/acceptance/virtio-gpu.py: combine kernel command line
tests/acceptance/virtio-gpu.py: use virtio-vga-gl
tests/acceptance/virtio-gpu.py: provide kernel and initrd hashes
tests/acceptance/virtio-gpu.py | 42 ++++++++++++----------------------
1 file changed, 15 insertions(+), 27 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-14 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 17:40 Cleber Rosa [this message]
2021-07-14 17:40 ` [PATCH 1/6] tests/acceptance/virtio-gpu.py: use require_accelerator() Cleber Rosa
2021-07-14 21:51 ` Willian Rampazzo
2021-07-14 17:40 ` [PATCH 2/6] tests/acceptance/virtio-gpu.py: combine x86_64 arch tags Cleber Rosa
2021-07-14 21:52 ` Willian Rampazzo
2021-07-14 17:40 ` [PATCH 3/6] tests/acceptance/virtio-gpu.py: combine CPU tags Cleber Rosa
2021-07-14 21:53 ` Willian Rampazzo
2021-07-14 17:40 ` [PATCH 4/6] tests/acceptance/virtio-gpu.py: combine kernel command line Cleber Rosa
2021-07-14 21:54 ` Willian Rampazzo
2021-07-14 17:40 ` [PATCH 5/6] tests/acceptance/virtio-gpu.py: use virtio-vga-gl Cleber Rosa
2021-07-14 21:55 ` Willian Rampazzo
2021-07-20 9:36 ` Marc-André Lureau
2021-07-21 12:14 ` Gerd Hoffmann
2021-07-14 17:40 ` [PATCH 6/6] tests/acceptance/virtio-gpu.py: provide kernel and initrd hashes Cleber Rosa
2021-07-14 21:56 ` 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=20210714174051.28164-1-crosa@redhat.com \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=ehabkost@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).