From: Adrian Freihofer <adrian.freihofer@...> Removes the following warnings thrown by make && valgrind -s --leak-check=3Dfull ./ptest-runner -d tests/data2 =3D=3D4154390=3D=3D Invalid write

From: Adrian Freihofer <adrian.freihofer@...> make && valgrind -s --leak-check=3Dfull ./ptest-runner -d tests/data2 =3D=3D4154029=3D=3D HEAP SUMMARY: =3D=3D4154029=3D=3D in use at exit:

From: Adrian Freihofer <adrian.freihofer@...> Signed-off-by: Adrian Freihofer <adrian.freihofer@...> --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) create mode 100644

This patch series provides some memory management fixes and corrected return code handling for ptest-runner2. Adrian Freihofer (4): git: Extend the gitignore mem: Fix memleak for ptest_opts

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

In message: RE: [yocto-kernel-cache] [yocto-5.10] nxp-imx8: Enable IMX_SCU_SOC config on 16/07/2021 Wang, Xiaolei wrote: The original patch didn't have a branch specified, so it somehow managed

<steve=echodyne.com@...> wrote: there should be a config.log generated in this component's build directory which should have more information on what check failed and perhaps some

I don't have the skills to review this in detail but it sounds like a good step forward for many different reasons, thanks! Cheers, Richard

I am generating eSDK for my image which includes meta-qt layer for graphics. meta-qt uses python3 where as my meta layer uses python2 my meta layer uses python2-mako where as meta-qt layer uses

Trying to produce c++ versions of dmalloc libraries.The dmalloc recipe dmalloc_5.5.2.bb looks to be configured to build the c++ versions with: 'EXTRA_OECONF += "--enable-threads --enable-cxx

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: Bug Triage meeting Thursday July 22nd at 7:30am PDT

Thanks...

Not deleting the source tree is the default behaviour. It sounds like you've inherited rm_work, so if you want to not delete build trees after completion then add the recipe name to

Thanks Richard, I suspect you're right. I'm using fuse-overlayfs which I'm mounting with the 'noxattrs' option because the host is Fedora and its SELinux configuration interferes with yocto in other

Hi Alex, RP, Mark, I did some research on the subject in order to try to figure out what is going on. 1) I come to a similar conclusion with what found, but tried to look a bit deeper for the

All, YP M+ or high bugs which moved to a new milestone in WW29 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12937 Consistent naming scheme for

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

All, Below is the list as of top 50 bug owners as of the end of WW29 of who have open medium or higher bugs and enhancements against YP 3.4. There are 72 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

From 59ed46416217e0c0b44203bc58e472e4068dba83 Mon Sep 17 00:00:00 2001 From: Mingrui Ren <jiladahe1997@...> Date: Mon, 19 Jul 2021 23:02:19 +0800 Subject: [PATCH v2] Add a new