In order to handle large output add a thread for read from childs using a pipe and remove non-blocking option. Modify bash unittest to output large data and cover this scenario. [YOCTO

Modify testcase to validate the actual exit status. [YOCTO #14217] Signed-off-by: Aníbal Limón <anibal.limon@...> --- tests/data/fail/ptest/run-ptest | 3 +++ tests/utils.c

Fixes, $ ./ptest-runner -d ./tests/data bash Signed-off-by: Aníbal Limón <anibal.limon@...> --- utils.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git

HI, Building up a customization layer over the top of poke to install 3rd party RPM files at build time. These packages contain some basic global configuration changes for the destination environment.

All, YP M+ or high bugs which moved to a new milestone in WW12 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11449 Allow overriding classes to

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 42 bug owners as of the end of WW12 of who have open medium or higher bugs and enhancements against YP 3.3. There are 28 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Ah, I was referring to the DTB used by the Kernel (which u-boot can switch), not the DTB used by u-boot itself (which AFAIK is compiled into u-boot and cannot be changed). > >> >> >> >> >

Hi Joshua, Wait, it's only the dtb used by u-boot which is different in this case, the kernel uses a single dtb for both variants. Those probably get embedded inside the bootloader, in any case

In case anyone else is affected by this… I tried building inside a Docker container based on Ubuntu 20.04 (and the buildtools removed) and the CVE database was populated properly (and CVE reports

FWIW, I'd rather u-boot could automatcially detect what variant of the board it's running on and do the right thing (usually, just selecting the proper DTB from the FIT image). The only

I just sent out an as yet untested patch which may fix some of the quoting issues by using bleach. I'd still need to add it to the requirements file... Cheers, Richard

Instead of searching for "<", use bleach to sanity input to avoid any XSS issues. Signed-off-by: Richard Purdie <richard.purdie@...> --- Post/parser.py | 26

Why am I (only, seems) always answering NON YOCTO issues in the YOCTO thread??? ;-) _______ OK. The good sign about what U R talking is shown here: [ 0.000885] printk: console [tty1] enabled It

<yann.dirson@...> wrote: Sure it would! But then you'd have to get all the BSP layer maintainers to agree on that format and use it… :-/

Hi Yann, Thanks for the patch updates. I'll look at them soon. I feel exactly the same way. By default all arm64 kernels are configured with the one, in-kernel, generic arm64 defconfig. That gives

Sorry about the delay on this, we do really need to get this resolved. I'm wondering if we should replace the angled brackets test with https://github.com/mozilla/bleach which would then remove the

BTW, I'm also unclear on what to do next to better support those boards: with the default kernel config only a subset of the hardware is supported, and for state-of-the-art hw support we'll also need

From: Yann Dirson <yann@...> --- Changes from v1: split in two distinct machines: nanopi-m4 and nanopi-m4-= 2gb conf/machine/include/nanopi-m4.inc | 22 +++++++++++++++++++