linux/poky.git/meta/recipes-extended/ltp, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

ltp: upgrade 20250530 -> 20250930

2025-10-13T17:01:04+00:00

ChangeLog: https://github.com/linux-test-project/ltp/releases/tag/20250930 (From OE-Core rev: dd53cccdd11358398cf154ee8d0e529ff180adb1) Signed-off-by: Yi Zhao Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ltp: upgrade 20250130 -> 20250530

2025-07-31T09:48:35+00:00

Changelog: https://github.com/linux-test-project/ltp/releases/tag/20250530 (From OE-Core rev: 6ad236f2fb724798ed62f6ad5f78b51d57496caa) Signed-off-by: Liu Yiding Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ltp: Skip semctl08 when __USE_TIME64_REDIRECTS is defined

2025-07-28T13:51:50+00:00

When __USE_TIME64_REDIRECTS is defined, glibc redirects struct semid_ds to a 64-bit time-safe version that omits the sem_otime_high and sem_ctime_high fields. As a result, the case becomes invalid, leading to incorrect behavior. This patch adds a check to skip the test when __USE_TIME64_REDIRECTS is defined, ensuring the test only runs when the semid_ds structurally matches semid64_ds and the *_high fields are accessible. (From OE-Core rev: 07410b54660f75465df8d428844893cbd0c295ea) Signed-off-by: Jiaying Song Signed-off-by: Richard Purdie

meta: remove consecutive blank lines

2025-06-20T11:07:27+00:00

Some of them were introduced by mass-removal of S = WORKDIR/git assignments; rather than try to fix up (or redo) just these, I've run this sed command over the whole tree: sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc` The rationale is that more than one empty line is wasting vertical screen space, and does nothing for readability. (From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove S in recipes that fetch from git via setting BB_GIT_DEFAULT_DESTSUFFIX

2025-06-20T11:07:26+00:00

Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX is set to match S from bitbake.conf (which itself is set to match typical tarball releases). A few recipes are setting S to a sub-directory of the git tree and need to be adjusted accordingly. bzip2 recipe is fetching a tarball and separately cloning tests; adjust the recipe to put the latter into 'bzip2-tests', instead of 'git'. devupstream.bbclass no longer needs to rewrite S, and is adjusted accordingly. Adjust scripts/lib/recipetool/append.py to not hardcode 'git' as unpack destination. Adjust kernel-yocto.bbclass to use the git unpack variable instead of hardcoding 'git' (there's also removal of repetition of string constants and a correction of workdir/unpackdir mismatch in one of the if-else branches). Ensure build-appliance-image recipe does not use 'git' as checkout directory for poky repo, but rather explicitly name it 'poky'. Ensure reproducible.py code that looks for git repositories does not hardcode 'git' but uses the destination set by BB_GIT_DEFAULT_DESTSUFFIX. Ensure recipetool does not write out unneeded S settings into newly created recipes that fetch from git. Adjust selftest to not hardcode 'git' as unpack directory. (From OE-Core rev: f80c07019ddadaf9c5fb890faabfda7920ecd15e) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ltp: backport patch to fix compilation error for Skylake -march=x86-64-v3

2025-05-22T13:36:49+00:00

When the input compiler enables AVX, stack realignment requirements causes gcc to fail to omit %rbp use, due to which the test fails to clobber %rbp in inline asm. Disable AVX to build the test on x86_64 so that the test continues working. (From OE-Core rev: bbd3e7886e2ec5ab3578d618b28d007a80d917aa) Signed-off-by: Yogesh Tyagi Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ltp: don't use host objcopy

2025-03-05T21:26:54+00:00

The kernel/kvm test uses the host objcopy when building a payload, but the host objcopy might not know how to deal with target binaries: CC testcases/kernel/kvm/lib_host.o objcopy: Unable to recognise the format of the input file `kvm_svm03-payload.elf' make[3]: *** [ltp/testcases/kernel/kvm/Makefile:67: kvm_svm03-payload.o] Error 1 Solve this by using the host-prefixed objcopy binary. (From OE-Core rev: 74818f79bd9a206f77ae3d26b19657116fd956cc) Signed-off-by: Ross Burton Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

ltp: upgrade 20240930 -> 20250130

2025-03-03T18:01:29+00:00

* Drop 0001-sched_attr-Do-not-define-for-glibc-2.41.patch as it has been merged upstream. * Skip statmount02 case which does not work on musl. (From OE-Core rev: 5d72185e65aa0d9012913d9d095caceada7799d7) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

recipes: Drop ld-is-gold support

2025-02-10T13:03:57+00:00

Gold hasn't seen development in some time and is being dropped from binutils releases. Drop the small number of special cases for it we were carrying. This patch also turns off gold in the binutils recipe. (From OE-Core rev: a4addb9ab63011e7c604fc5daff95559e7d214e7) Signed-off-by: Richard Purdie