[yocto] M+ & H bugs with Milestone Movements WW38

All, YP M+ or high bugs which moved to a new milestone in WW38 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 13533 Devtool finish on _git package with SRCPV in PV points to wrong WORKDIR

[yocto] Enhancements/Bugs closed WW38!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.pur...@linuxfoundation.org 4 michael.opdenac...@bootlin.com 1 alexandre.bell...@bootlin.com 1 yi.z...@windriver.com 1 to...@cybernetics.com 1 qi.c...@windriver.com 1

[yocto] Current high bug count owners for Yocto Project 3.4

All, Below is the list as of top 50 bug owners as of the end of WW38 of who have open medium or higher bugs and enhancements against YP 3.4. There are 28 possible work days left until the final release candidates for YP 3.4 needs to be released. Who Count michael.opdenac...@bootlin.com 37

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 the triage page under the appropriate heading:

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

On Fri 2021-09-17 @ 06:01:21 PM, Trevor Woerner via lists.yoctoproject.org wrote: > Recent upstream kernel changes have made the mmc probing order unpredictable. > Therefore, boards with both an emmc and sdmmc interface aren't guaranteed to > boot with a hard-coded root device selected. > > For

Re: [yocto] Sharing sstate cache across build nodes

On Thu, 16 Sept 2021 at 05:34, Rusty Howell wrote: > Can SSTATE_DIR be shared across build hosts with different OS's (Ubuntu > 18.04, ubuntu 20.04, etc, RHEL)? If you don't use uninative, then the sstate can be in a single directory but artifacts won't be shared. If you use uninative then the

Re: [yocto] [PATCH v2 ptest-runner 2/2] main: Do not return number of failed tests when calling ptest-runner

I think we might be having an 'unresponsive maintainer' situation? How can Anibal be reached? Alex On Mon, 20 Sept 2021 at 11:19, ?ukasz Majewski wrote: > Hi Anibal, > > > Hi Anibal, > > > > > Up till now ptest-runner2 returns number of failed tests with its > > > exit status code. Such use

Re: [yocto] [PATCH v2 ptest-runner 2/2] main: Do not return number of failed tests when calling ptest-runner

Hi Anibal, > Hi Anibal, > > > Up till now ptest-runner2 returns number of failed tests with its > > exit status code. Such use case is not recommended [1] and may cause > > issues when there are more than 256 tests to be executed. > > > > To alleviate this issue the number of total tests with