From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [OE-core][PATCH] wayland: Remove event_loop_timer test
Date: Thu, 6 Nov 2025 08:50:21 -0700 [thread overview]
Message-ID: <20251106155021.16738-1-JPEWhacker@gmail.com> (raw)
The event_loop_timer test requires precise timing constraints (10's of
milliseconds) which cannot be achieved on qemu testing targets. Remove
this test to prevent spurious failures.
[YOCTO #14861]
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
...1-tests-Remove-event_loop_timer-test.patch | 42 +++++++++++++++++++
.../wayland/wayland_1.24.0.bb | 1 +
2 files changed, 43 insertions(+)
create mode 100644 meta/recipes-graphics/wayland/wayland/0001-tests-Remove-event_loop_timer-test.patch
diff --git a/meta/recipes-graphics/wayland/wayland/0001-tests-Remove-event_loop_timer-test.patch b/meta/recipes-graphics/wayland/wayland/0001-tests-Remove-event_loop_timer-test.patch
new file mode 100644
index 0000000000..e662d6cfd2
--- /dev/null
+++ b/meta/recipes-graphics/wayland/wayland/0001-tests-Remove-event_loop_timer-test.patch
@@ -0,0 +1,42 @@
+From 61fa7e7d9c282798988907cf3b8928c88d7a7930 Mon Sep 17 00:00:00 2001
+From: Joshua Watt <JPEWhacker@gmail.com>
+Date: Thu, 6 Nov 2025 08:35:26 -0700
+Subject: [PATCH] tests: Remove event_loop_timer test
+
+The event_loop_timer tests relies on very precise timing of the
+execution (10's of milliseconds). However, on the Yocto Autobuilder qemu
+testing, this sort of precise timing is not possible, resulting in
+spurious test failures.
+
+Remove this test to prevent these failures, since there isn't a simple
+way to increase the timing constraints.
+
+Upstream-Status: Inappropriate [oe-specific]
+Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
+---
+ tests/event-loop-test.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/tests/event-loop-test.c b/tests/event-loop-test.c
+index a51ba8f..0c39b09 100644
+--- a/tests/event-loop-test.c
++++ b/tests/event-loop-test.c
+@@ -238,6 +238,7 @@ TEST(event_loop_multiple_same_signals)
+ wl_event_loop_destroy(loop);
+ }
+
++#if 0 /* Timing requirements are too tight for qemu testing */
+ static int
+ timer_callback(void *data)
+ {
+@@ -280,6 +281,7 @@ TEST(event_loop_timer)
+ wl_event_source_remove(source2);
+ wl_event_loop_destroy(loop);
+ }
++#endif
+
+ #define MSEC_TO_USEC(msec) ((msec) * 1000)
+
+--
+2.51.1
+
diff --git a/meta/recipes-graphics/wayland/wayland_1.24.0.bb b/meta/recipes-graphics/wayland/wayland_1.24.0.bb
index 5fb7951781..de7ee516bb 100644
--- a/meta/recipes-graphics/wayland/wayland_1.24.0.bb
+++ b/meta/recipes-graphics/wayland/wayland_1.24.0.bb
@@ -15,6 +15,7 @@ DEPENDS = "expat libffi wayland-native"
SRC_URI = "https://gitlab.freedesktop.org/wayland/wayland/-/releases/${PV}/downloads/${BPN}-${PV}.tar.xz \
file://run-ptest \
file://0001-build-Fix-strndup-detection-on-MinGW.patch \
+ file://0001-tests-Remove-event_loop_timer-test.patch \
"
SRC_URI[sha256sum] = "82892487a01ad67b334eca83b54317a7c86a03a89cfadacfef5211f11a5d0536"
--
2.51.1
reply other threads:[~2025-11-06 15:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251106155021.16738-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox