I'm guessing a lot of people don't follow the intermittent issues. I therefore thought I'd share a summary of some of them along with some random thoughts on them. There is a mix of different things

It would seem reasonable although hardknott is due to have it's final build soon. Cheers, Richard

The following supported versions have the same problem, should we also fix them? Dunfell Hardknott Honister I'd like to send the patches after testing if we need fix them. // Robert

I don't know why it was set to proprietary in the test but it doesn't seem to cause any regressions so I removed it. It is at an older version which should mean it doesn't affect other builds so I'm

Hi RP, Thank you very much, I'm trying to run the test cases, but I found that you've already fixed them, thanks again. // Robert

This isn't what I meant. I meant something like: REQUIRED_DISTRO_FEATURES = 'ptest' inherit features_check Cheers, Richard

I ran this through the autobuilder as requested as it means we have a chance to get things fixed upstream before gcc 12 is

Hi Richard, Thanks very much for mentioning the correct way of fixing the issue. The modified patch is posted as:- https://lists.openembedded.org/g/openembedded-core/message/164524 Please let me

The current default DISTRO_FEATURES does not support ptest. Hence, the following error is generated during "bitbake glibc-tests". ERROR: glibc-tests-2.35-r0 do_package: QA Issue:

Signed-off-by: Changhyeok Bae <changhyeok.bae@...> --- .../recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch | 2 +- .../ethtool/{ethtool_5.16.bb => ethtool_5.17.bb} |

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

Recipe upgrade statistics: * Failed(do_compile): 12 u-boot-tools, 2022.04, Marek Vasut <marek.vasut@...> u-boot, 2022.04, Marek Vasut <marek.vasut@...>

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

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

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libgcrypt* to *1.10.1* has Failed(do_compile). Detailed error

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shared-mime-info* to *2.2* has Succeeded. Next steps: - apply the patch: git am

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

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libgpg-error* to *1.45* has Failed (devtool error). Detailed error

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

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *at-spi2-core* to *2.44.0* has Failed (devtool error). Detailed error