In order to debug these selftest failures you end up having to comment out the file cleanup. Make this an option at the top of the file to make it a bit easier, I've had to do this too many times now.

The SPDX class doens't get on well with non-standard licenses. Disable it for the purposes of this test to avoid errors. Add a new helper function to the core test code to allow this to be done easily

Other changes in create-spdx code mean we shouldn't need to do this now. We need the various exclusions to allow the task hashes to behave correctly for the SPDX tasks too. Signed-off-by: Richard Purd

Add a dependency which should have been in this list but wasn't, found when debugging create-spdx hash issues. Signed-off-by: Richard Purdie <richard.purdie@...> --- meta/conf/layer.conf | 1 + 1 file

Some variables cause issues with taskhashes and are accounted for in the output in other ways, or don't affect it. Exclude these to improve the taskhashes with create-spdx and allow the sstate selftes

There are two seperate PKGDATA_DIR directories, one for the target and one for the SDK. Rather than fail when a package can't be found, try the SDK first. We use a datastore copy to keep the code simp

From: Joshua Watt <JPEWhacker@...> Fixes the runtime dependency calculations to also only follow direct dependencies of the current task instead of all transient dependencies in a similar way as the b

From: Joshua Watt <JPEWhacker@...> Build time dependencies were not being correctly calculated for SPDX documents because while a task can `deptask` itself (as do_create_spdx did), those dependencies

From: Joshua Watt <JPEWhacker@...> If a package renames itself using PKG, the new name should be respected as a name that the recipe provides. Signed-off-by: Joshua Watt <JPEWhacker@...> Signed-off-by

From: Joshua Watt <JPEWhacker@...> Enabling the SPDX class and running two builds, one with SDKMACHINE=i686 and then again with SDKMACHINE=x86_64 would lead to errors since the output was stored per M

Move target stop (for Qemu targets: qemu image stop) later in testimage main function, especially _after_ having access to general test results, to allow executing some other actions (like retrieving

Mtd-utils has internal libraries (libmtd and libubi) that simplify the usage and access, and they can be used by applications to access MTD devices without reinventing the code. Signed-off-by: Stefano

This series is a proposal to bring in an "artifact retriever" to ease debugging when some runtime tests fails. This is a follow-up to corresponding RFC ([1]), which in turn is a proposal to address ge

From: Khem Raj <raj.khem@...> - Remove already upstreamed patches - Brings a list of changes [1] [2] [3] [1] https://github.com/golang/go/issues?q=milestone%3AGo1.20.2+label%3ACherryPickApproved [2] h

From: Khem Raj <raj.khem@...> Fixes go: ELF binary /usr/lib/go/pkg/tool/linux_arm64/pprof has relocations in .text go: ELF binary /usr/lib/go/bin/go has relocations in .text [textrel] Signed-off-by: K

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *alsa-utils* to *1.2.9* has Failed(do_compile). Detailed error information: do_compile

From: duep <duep.fnst@...> Add a ptest for xz - It is taking around 1s to execute with kvm, so added it to PTESTS_FAST - It contains 11 test files: test_bcj_exact_size test_block_header test_check tes

AUH finished upgrade batch the result patches/logs can be found at: https://autobuilder.yocto.io/pub/auh/20230601050105, next are the statistics: Recipe upgrade statistics: * Failed(do_compile): 21 gn

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *sqlite3* to *3.42.0* has Succeeded. Next steps: - apply the patch: git am 0001-sqlite

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *serf* to *1.3.10* has Succeeded. Next steps: - apply the patch: git am 0001-serf-upgr