From: Armin Kuster <akuster@...> Source: https://github.com/SELinuxProject/selinux/ MR: 111857 Type: Security Fix Disposition: Backport from

From: Armin Kuster <akuster@...> Source: https://github.com/SELinuxProject/selinux MR: 111851 Type: Security Fix Disposition: Backport from

From: Armin Kuster <akuster@...> Source: https://github.com/SELinuxProject/selinux MR: 111869 Type: Security Fix Disposition: Backport from

From: Armin Kuster <akuster@...> Source: https://github.com/SELinuxProject/selinux/ MR: 111857 Type: Security Fix Disposition: Backport from

From: Armin Kuster <akuster@...> Source: https://github.com/SELinuxProject/selinux MR: 111851 Type: Security Fix Disposition: Backport from

Cheers, will add now. Also, dmesg will be collected and archived through a separate channel, and regardless of whether something is stuck or not

It is great to see this. I'd suggest dmesg in here since we've seen components of tests segfault before (e.g. lttng-relayd in lttng-tools). Cheers, Richard

Correction: AB-INT bug count is at 52.

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alex, Diane, Jon, Joshua, Michael, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: - Trevor to

Currently, ptest-runner simply kills the offending test without further ado, which is not at all helpful when trying to figure out why it happens (especially if such hangs are intermittent and rare).

if poll()'s timeout expires that means the test did not produce any output, which is exactly what we need to catch. So there's no need to set up separate timeouts with signals and alarms, and this

I also took the opportunity to correct a weird API that returns a result (or not), depending on some internal condition. Signed-off-by: Alexander Kanavin <alex@...> --- tests/utils.c | 35

Fixed: $ ./update.py -b hardknott,master ERROR: Variable PREMIRRORS_append contains an operation using the old override syntax. Please convert this layer/metadata before attempting to use with a

A build flagged for QA (yocto-3.1.11.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.11.rc2 Build hash information: bitbake:

yes if you use uninative ( which is default in poky) then it should be able to share across multiple build hosts. if you preserve PR server data then you should be good. sstate can be regenerated.

Thanks for the replies, Richard. Can SSTATE_DIR be shared across build hosts with different OS's (Ubuntu 18.04, ubuntu 20.04, etc, RHEL)? Our build hosts are somewhat ephemeral. Occasionally we

Below is an accidental DM between Richard and myself. I am posting it here for others. > When setting up a shared sstate cache via NFS, do all the build hosts have > read/write access to the sstate

I also took the opportunity to correct a weird API that returns a result (or not), depending on some internal condition. Signed-off-by: Alexander Kanavin <alex@...> --- tests/utils.c | 35

The rock64 has an ARM Mali 450 MP2 GPU, therefore enable mesa's lima for accelerated, open-source graphics. Signed-off-by: Trevor Woerner <twoerner@...> ---

It looks like we'll need to do an rc2 build to pick up a patch for meta-yocto. Thanks to Denys for noticing the issue! For details