linux/poky.git/meta/lib, branch yocto-4.1.2

oeqa/concurrencytest: Add number of failures to summary output

2023-01-06T17:33:19+00:00

When running oe-selftest and seeing the end of a running log, it is extremely helpful to know if there have been failures or not to save looking at the rest of the log. Add the number of failures to the summary line so that people monitoring builds have an easier time before the end totals are printed. (From OE-Core rev: 80ac9e2eddd4b8b87c2978b3238ac16db2c55e43) Signed-off-by: Richard Purdie (cherry picked from commit 6b23996911d91f7f99774646c6db9f3490b4cb62) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/selftest/externalsrc: add test for srctree_hash_files

2022-12-23T23:05:57+00:00

(From OE-Core rev: 3cdcd2ce80daaa4a49471e483bd7863803fa6388) Signed-off-by: Peter Marko Signed-off-by: Alexandre Belloni (cherry picked from commit 7b9728e5b8bdf1193c1304ec3beeca4b5bf8d2da) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/selftest/tinfoil: Add test for separate config_data with recipe_parse_file()

2022-12-23T23:05:57+00:00

We've seen two different regressions in this API since it is used by layer-index but not be the core code. Add a test for it to try and ensure we don't break it again. (From OE-Core rev: 82e2b21f4a91c03203178a4d927c7c7feb930785) Signed-off-by: Richard Purdie Signed-off-by: Alexandre Belloni (cherry picked from commit b07de5de43ec9c9a2c5d496a64940ccdc5b47cf8) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

sstatesig: emit more helpful error message when not finding sstate manifest

2022-12-07T15:02:50+00:00

Since oe-core commit 64b89f3c8fc31842256c482a3039d90d3f12c1cc ("sstatesig.py: make it fatal error when sstate manifest isn't found") errors like: | Manifest [..]/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-dbus.populate_sysroot not found in imx8mm_dummy cortexa53-mx8mm cortexa53 armv8a-crc armv8a aarch64 allarch x86_64_x86_64-nativesdk (variant '')? are fatal now and cannot be ignored but must be debugged. Unfortunately, the currently emitted error message is a bit imprecise with telling the reader what has actually gone wrong. This commit: * adds the word 'sstate' to the error message to clarify the scope we are dealing with ('sstate manifests', since there are other manifests, too) * does not randomly print the last manifest file searched for as THE manifest file that could not be found Instead, we print the name of the task the sstate was searched for * adds the word 'multilib' to variant to make clear which variant we are talking about * adds a separate line noting the searched pkgarchs and adds explicitly mentions this word ('pkgarchs') * prints a list of ALL manifest file locations attempted * removes the '?' at the end of the message since such errors indeed leave the question of what is the cause but the error message itself is more like a statement. The result for the exact same issue as noted above then looks as follows: | The sstate manifest for task 'dbus:populate_sysroot' (multilib variant '') could not be found. | The pkgarchs considered were: imx8mm_dummy, cortexa53-mx8mm, cortexa53, armv8a-crc, armv8a, aarch64, allarch, x86_64_x86_64-nativesdk. | But none of these manifests exists: | [..]/tmp/sstate-control/manifest-imx8mm_dummy-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-cortexa53-mx8mm-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-cortexa53-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-armv8a-crc-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-armv8a-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-aarch64-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-allarch-dbus.populate_sysroot | [..]/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-dbus.populate_sysroot (From OE-Core rev: 18f1a5554063b0cecd206abed6e57f397f7d1346) Signed-off-by: Enrico Jorns Signed-off-by: Alexandre Belloni (cherry picked from commit 735ec126ec219c7cb89cb05b0e433201bb7f59eb) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

sstatesig: skip the rm_work task signature

2022-12-01T19:35:11+00:00

We can skip the rm_work task signature to avoid running the task when we remove some tasks from the dependencie chain. The inject_rm_work handler on the rm_work bbclass triggers the rm_work task running for any signature change in the dependencie chain of the task do_build of each recipe. i.e INHERIT:remove = "create-spdx" will trigger the do_rm_work when we collect the sstate cache with INHERIT = "create-spdx" (From OE-Core rev: f1f8f894048b325ce9a8af03b1c3b1c5a9c1f983) Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni (cherry picked from commit 292305700e39d0ebd64763f5032c39ace5005fad) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/selftest/lic_checksum: Cleanup changes to emptytest include

2022-12-01T19:35:11+00:00

Config written to the emptytest include file is invalid after the test has cleaned up its temporary directories resulting in the emptytest recipe potentially having invalid content when parsed by successive bitbake runs. This presents the following error in tests after lic_checksum execution, e.g. 'oe-selftest -r lic_checksum recipetool' ERROR: .../emptytest.bb: Unable to get checksum for emptytest SRC_URI entry tmpn_nyosnq: file could not be found Remove the recipe include content once the bitbake runs are completed in each lic_checksum test case. (From OE-Core rev: 34ff6190581258c7fa2786a71196703a35d9d5e3) Signed-off-by: Nathan Rossi Signed-off-by: Alexandre Belloni (cherry picked from commit 087df767a64b271b503d714df3df6d8b3caad1c0) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

selftest: add a copy of previous mtd-utils version to meta-selftest

2022-12-01T19:35:10+00:00

The latest version update eliminated all custom patches, and the selftest expects them. (From OE-Core rev: fd70a508b75d403822448907033ed6f655fcbe9b) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni (cherry picked from commit 95298a7f1ad29c0fc0d02772d646116709ac355f) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

oeqa/runtime/dnf: rewrite test_dnf_installroot_usrmerge

2022-11-24T15:30:06+00:00

This test doesn't get exercised on the autobuilder and so it was broken: specifically some of the ln commands silently fail and the chroot isn't usable. Rewrite the test case to correctly construct a chroot so the test can pass. (From OE-Core rev: 6f5e10d682be54a70456c4cea9abbde4add1fead) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit bb6ebb9956a42df3ed8681aec9aedf340b12f934) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

rust-target-config: match riscv target names with what rust expects

2022-11-09T17:42:14+00:00

Official rust risc-v targets are prefixed with riscv32gc- and riscv64gc-: https://doc.rust-lang.org/nightly/rustc/platform-support.html Particularly crossbeam-utils make important build time decisions for atomics based on those names, and so we need to match ours with official targets. On the other hand, the actual definitions for those targets do not use the 'gc' suffix in 'arch' and 'llvm-target' fields, and so we need to follow that too, to avoid cryptic mismatch errors from rust-llvm: https://github.com/rust-lang/rust/blob/master/compiler/rustc_target/src/spec/riscv32gc_unknown_linux_gnu.rs (From OE-Core rev: 2daa8d76369cd06e5c357e393e3145e08f3d6760) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 1cfb9c8a59d98ccc9b0510cd28fb933f72fb6b6c) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

buildconf: compare abspath

2022-11-09T17:42:14+00:00

We have something like ${TOPDIR}/../../poky/meta in the bblayers.conf file. This does not work without normalizing the path for comparison. (From OE-Core rev: 803975aff35c9423f4bde4c0201d0f61242389e0) Signed-off-by: Adrian Freihofer Signed-off-by: Alexandre Belloni (cherry picked from commit e0d45bcd34311ae248bac9378f46962198d148ef) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie