]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core.git/commit
glibc-y2038-tests: remove glibc-y2038-tests_2.41.bb recipe
authorrajmohan r <semc.2042@gmail.com>
Tue, 29 Apr 2025 07:32:12 +0000 (13:02 +0530)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 1 May 2025 13:20:18 +0000 (14:20 +0100)
commitfbe3679ba3c12c52a502511f5dde91fb4de7a6b6
treebacb816d4f61c6d3ab915cfb32a3b0734fd8a52b
parent7b3563b3b3901c96c3e498799a83ab8cabcf84b4
glibc-y2038-tests: remove glibc-y2038-tests_2.41.bb recipe

This recipe takes longer time >20min when bitbake for package
write stage. When cross-verified for longer time duration, found
that do_check() stage taking 20min while other stages completes
before 6min.

This recipe gives only below two test binaries in the packages to
test (ptest: glibc-y2038-tests):
     io/ftwtest
     io/ftwtest-time64

The above test binaries are already included for testing in recipe
glibc-testsuite_2.41.bb.

It is by now well established that glibc itself works as it should,
that all affected 32 bit targets are configured to use 64 bit time_t,
and that any lingering y2038 issues are in components other than the c
library, and usually come from C programming mistakes (e.g. storing
timestamps in long). Maybe we can simply remove the recipe?

Review comments for fixing above longer time duration ended up in
removing this recipe as a proposal is below
https://lists.openembedded.org/g/openembedded-core/topic/112188476#msg214636

Removed lines having reference to glibc-y2038-tests in the files.

Signed-off-by: rajmohan r <semc.2042@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/conf/distro/include/maintainers.inc
meta/conf/distro/include/ptest-packagelists.inc
meta/conf/distro/include/time64.inc
meta/recipes-core/glibc/glibc-y2038-tests_2.41.bb [deleted file]
meta/recipes-core/glibc/glibc/run-ptest [deleted file]