From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-arm@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: [PATCH 0/1] tests/acceptance: Count Raspberry Pi logos displayed on framebuffer
Date: Sat, 1 Feb 2020 00:24:35 +0100 [thread overview]
Message-ID: <20200131232436.23548-1-f4bug@amsat.org> (raw)
This is a simple Avocado test that use OpenCV to find the
4 Raspberry Pi logo on the framebuffer screen dump.
The resulting match can be visualised at:
https://pasteboard.co/ISzNHtx.png
It is very fast, around 11 seconds on my laptop.
The test probably won't stay in boot_linux_console.py but will
go into tests/acceptance/machine_arm_raspi.py, but I wanted to
show this test could work to test SMP CPUs.
Similar test: "integratorcp: Verify Tux is displayed on framebuffer"
https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg08103.html
Philippe Mathieu-Daudé (1):
tests/acceptance: Count Raspberry Pi logos displayed on framebuffer
tests/acceptance/boot_linux_console.py | 62 ++++++++++++++++++++++++++
1 file changed, 62 insertions(+)
--
2.21.1
next reply other threads:[~2020-01-31 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 23:24 Philippe Mathieu-Daudé [this message]
2020-01-31 23:24 ` [PATCH 1/1] tests/acceptance: Count Raspberry Pi logos displayed on framebuffer Philippe Mathieu-Daudé
2020-02-03 14:21 ` Wainer dos Santos Moschetta
2020-02-03 15:48 ` Eduardo Habkost
2020-02-03 16:08 ` Philippe Mathieu-Daudé
2020-02-04 16:57 ` Wainer dos Santos Moschetta
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=20200131232436.23548-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).