[PATCH 1/5] lttng-tools: ensure that ptest errors are not suppressed

[PATCH 1/5] lttng-tools: ensure that ptest errors are not suppressed

[Alexander Kanavin]

From: Alexander Kanavin <alex@linutronix.de>

At some recent point lttng-tools ptests have quietly regressed,
and most of them aren't executed anymore. Errors are printed
on the console, but aren't reported as exit code from run-ptest.

The reason is that exitcode was set to what sed returned, not make.
The original reason for piping through sed was to unify /tmp/tmp.xxxx outputs
for easier results comparison, but (after fixing the tests) I don't
see such lines anymore, and in any case ensuring such regressions
are caught is more important.

With this fix, run-ptest and testimage starts to fail as it should.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 meta/recipes-kernel/lttng/lttng-tools/run-ptest | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/lttng/lttng-tools/run-ptest b/meta/recipes-kernel/lttng/lttng-tools/run-ptest
index f4f7a3baea..e7edc03e96 100755
--- a/meta/recipes-kernel/lttng/lttng-tools/run-ptest
+++ b/meta/recipes-kernel/lttng/lttng-tools/run-ptest
@@ -31,7 +31,7 @@ validate_lttng_modules_present || {
 make -k -t all >error.log 2>&1
 # Can specify a test e.g.:
 # -C tests/regression/ check TESTS='kernel/test_callstack'
-make -k -s $makeargs check 2>error.log | sed -e 's#/tmp/tmp\...........#/tmp/tmp.XXXXXXXXXX#g'
+make -k -s $makeargs check 2>error.log
 exitcode=$?
 if [ -e error.log ]; then
     cat error.log
-- 
2.47.3

[PATCH 2/5] lttng-tools: add missing python3-multiprocessing dependency to ptests

[Alexander Kanavin]

From: Alexander Kanavin <alex@linutronix.de>

This restores the not-running tests, and everything is again able
to run (and pass).

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb b/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb
index 46bf59c271..1106867aeb 100644
--- a/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb
+++ b/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb
@@ -15,7 +15,7 @@ include lttng-platforms.inc
 DEPENDS = "liburcu popt libxml2 util-linux bison-native babeltrace2"
 RDEPENDS:${PN} = "libgcc"
 RRECOMMENDS:${PN} += "${LTTNGMODULES}"
-RDEPENDS:${PN}-ptest += "make perl bash gawk procps perl-module-overloading coreutils util-linux kmod ${LTTNGMODULES} sed python3-core grep binutils"
+RDEPENDS:${PN}-ptest += "make perl bash gawk procps perl-module-overloading coreutils util-linux kmod ${LTTNGMODULES} sed python3-core grep binutils python3-multiprocessing"
 RDEPENDS:${PN}-ptest:append:libc-glibc = " glibc-utils"
 RDEPENDS:${PN}-ptest:append:libc-musl = " musl-utils"
 # babelstats.pl wants getopt-long
-- 
2.47.3

[PATCH 3/5] lttng-tools: install .expect test files with a wildcard

[Alexander Kanavin]

From: Alexander Kanavin <alex@linutronix.de>

Otherwise, there will be failures on 32 bit hosts. Note
that the needed files are erroneously absent from upstream
release tarballs:
https://bugs.lttng.org/issues/1436
but once that is resolved, this commit will be effective.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb b/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb
index 1106867aeb..620ddfb1cf 100644
--- a/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb
+++ b/meta/recipes-kernel/lttng/lttng-tools_2.14.1.bb
@@ -90,8 +90,8 @@ do_install_ptest () {
     for f in Makefile tests/Makefile tests/utils/utils.sh tests/regression/tools/save-load/*.lttng \
             tests/regression/tools/save-load/configuration/load-42*.lttng tests/regression/tools/health/test_health.sh \
             tests/regression/tools/metadata/utils.sh tests/regression/tools/rotation/rotate_utils.sh \
-            tests/regression/tools/trace-format/ust-local-trace-pretty.expect \
-            tests/regression/tools/trace-format/kernel-local-trace-pretty.expect \
+            tests/regression/tools/trace-format/ust-local-trace-pretty.expect* \
+            tests/regression/tools/trace-format/kernel-local-trace-pretty.expect* \
             tests/regression/tools/base-path/*.lttng; do
         install -D "${B}/$f" "${D}${PTEST_PATH}/$f"
     done
-- 
2.47.3

[PATCH 4/5] time64.inc: clean up and add upstream tickets where issues remain

[Alexander Kanavin]

From: Alexander Kanavin <alex@linutronix.de>

Most issues were resolved via upstream version updates that bring in
needed fixes:

glib-2.0 update to 2.78.0 that includes:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3547
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3550

curl update to 8.3.0 that includes
https://github.com/curl/curl/pull/11610

util-linux update to 2.39 that includes
https://github.com/util-linux/util-linux/pull/2430
https://github.com/util-linux/util-linux/commit/3ab9e699a8d90f55e0447516b7e05a8686180467
https://github.com/util-linux/util-linux/pull/2435

glib-networking update to 2.78.0 that includes
https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/241

python3-cryptography update to 42.0.0 which resolves
https://github.com/pyca/cryptography/issues/9370 via
https://github.com/pyca/cryptography/pull/9964

perl update to 5.40.0 which includes
https://github.com/Perl/perl5/pull/21379

python3 update to 3.13.0 which includes
https://github.com/python/cpython/pull/118425
python3 update to 3.13.1 which includes
https://github.com/python/cpython/pull/124972
python3 update to 3.14.0 which includes
https://github.com/python/cpython/pull/119401
https://github.com/python/cpython/pull/125045
https://github.com/python/cpython/pull/107594
https://github.com/python/cpython/pull/125104

tcl update to 9.0.0 which includes
https://github.com/tcltk/tcl/commit/4ca61724c554f02d90a0655da81372bfbb34f70d
(tcl8 recipe has a simple backport of this)

dbus update to 1.16.0 which includes
https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/444
https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/289

openssh update to 10.0p1 which includes
https://github.com/openssh/openssh-portable/pull/425
https://bugzilla.mindrot.org/show_bug.cgi?id=3684
https://marc.info/?l=openbsd-bugs&m=172561736524815&w=2
https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-October/041621.html
(all reporting the same issue)

gcc update to 15.1 which includes
https://github.com/llvm/llvm-project/pull/99699
via https://github.com/gcc-mirror/gcc/commit/fa321004f3f6288d3ee2eefa6b02177131882dca
and allows dropping special flags and exceptions for gcc-sanitizers.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 meta/conf/distro/include/time64.inc | 21 ++++++++++++++-------
 1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/meta/conf/distro/include/time64.inc b/meta/conf/distro/include/time64.inc
index 3ed0a4253d..5a2a3fbe81 100644
--- a/meta/conf/distro/include/time64.inc
+++ b/meta/conf/distro/include/time64.inc
@@ -2,11 +2,22 @@
 # QB_OPT_APPEND:append = " -rtc base=2040-02-02"
 #
 # Note that this does result in ptest failures on qemux86:
-# perl python3 dbus openssl glibc-tests openssh curl glib-2.0 tcl libmodule-build-perl
-# and a subset of those occurs in qemux86-64 as well:
-# curl python3 openssl openssl tcl python3-cryptography
+#
+#   (none known at this point)
+#
+# and some ptest failures appear in qemux86-64 as well:
+#
+#   openssl https://github.com/openssl/openssl/issues/21671
 #
 # Working to address those (before Y2038 rolls in) will be appreciated.
+#
+# Note: some issues occur on 32 bit regardless of the date set:
+#
+#   lttng-tools:
+#   https://bugs.lttng.org/issues/1436
+#   FAIL: tests.serial 59 - Test script 'ust/blocking/test_blocking' returned code 255.
+#   (due to lack of space on /tmp, which is due to a non-highmem kernel, which allocates only 800M of RAM to userspace)
+#
 
 GLIBC_64BIT_TIME_FLAGS = "${GLIBC_64BIT_TIME_FLAGS_WHEN_NEEDED}"
 
@@ -21,12 +32,8 @@ TARGET_CC_ARCH:append:x86 = "${@bb.utils.contains('TUNE_FEATURES', 'm32', '${GLI
 
 GLIBC_64BIT_TIME_FLAGS:pn-glibc = ""
 GLIBC_64BIT_TIME_FLAGS:pn-glibc-testsuite = ""
-# Undefines _FILE_OFFSET_BITS on purpose in
-# libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp
-GLIBC_64BIT_TIME_FLAGS:pn-gcc-sanitizers = ""
 
 # Caused by the flags exceptions above
-INSANE_SKIP:append:pn-gcc-sanitizers = " 32bit-time"
 INSANE_SKIP:append:pn-glibc = " 32bit-time"
 
 # Strace has tests that call 32 bit API directly, which is fair enough, e.g.
-- 
2.47.3

[PATCH 5/5] time64.inc: add links to "Y2038 in Yocto" slides and video

[Alexander Kanavin]

From: Alexander Kanavin <alex@linutronix.de>

I'm not sure if placing conference slides and video links
here is okay, but I believe this is the best starting point
for anyone dealing with the Y2038 problem. It will help and
provide important context and action points for those needing
to support 32 bit products beyond Y2038.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 meta/conf/distro/include/time64.inc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/meta/conf/distro/include/time64.inc b/meta/conf/distro/include/time64.inc
index 5a2a3fbe81..19177b1f3c 100644
--- a/meta/conf/distro/include/time64.inc
+++ b/meta/conf/distro/include/time64.inc
@@ -1,3 +1,8 @@
+# An overview of Y2038 issues, and how to prepare a yocto-based
+# product for that date is available at
+# https://www.youtube.com/watch?v=eaOHJHFMobw
+# https://osseu2024.sched.com/event/1ej4C/
+#
 # To simulate Y2038 occurring in qemu, add to your build configuration:
 # QB_OPT_APPEND:append = " -rtc base=2040-02-02"
 #
-- 
2.47.3