diff options
author | rajmohan r <semc.2042@gmail.com> | 2025-05-12 22:37:43 +0530 |
---|---|---|
committer | Steve Sakoman <steve@sakoman.com> | 2025-05-19 08:32:49 -0700 |
commit | 2a501e4f1b8120c73f581715430bae263d1c0b60 (patch) | |
tree | 2188d25a17cd1c5134ab68661f32a7309823c7ac /scripts/lib/devtool/runqemu.py | |
parent | 848da2f632f22fa4934d74838c731ed9352a1816 (diff) | |
download | poky-2a501e4f1b8120c73f581715430bae263d1c0b60.tar.gz |
glibc-y2038-tests: remove glibc-y2038-tests_2.39.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.39.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). So this recipe seems to be redundant and
can be removed.
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.
For master branch requested for integration and below is the link
https://lists.openembedded.org/g/openembedded-core/message/215655
(From OE-Core rev: b214cc84a922f7a3fb7ebbc501189ce25e8bd2bd)
Signed-off-by: rajmohan r <semc.2042@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'scripts/lib/devtool/runqemu.py')
0 files changed, 0 insertions, 0 deletions