Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M3.rc9)

On Mon, 2023-10-02 at 09:41 +, Jing Hui Tham wrote: > Hi all, > > Intel and WR YP QA is planning for QA execution for YP build > yocto-4.3_M3.rc9. We are planning to execute following tests for this cycle: > > OEQA-manual tests for following module: > 1. OE-Core > 2. BSP-hw > > Runtime

Re: [yocto] [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

On Fri, 2023-09-29 at 14:06 +0200, Alexander Kanavin wrote: > On Thu, 28 Sept 2023 at 18:49, Richard Purdie > wrote: > > > I'm curious to see what you find with analysis of bitbake-whatchanged. > > I've taken a look a the script. It obtains the current location of &g

Re: [yocto] [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

On Thu, 2023-09-28 at 18:43 +0200, Alexander Kanavin wrote: > On Fri, 22 Sept 2023 at 12:42, Richard Purdie > wrote: > > > Things which used to be problematic: > > > > a) changes involving changes to gcc-source since it uses a shared > > sources stamps which

Re: [yocto] [PATCH][yocto-autobuilder-helper] config.json: add reproducible-openembedded build

On Thu, 2023-09-28 at 15:18 +0200, Fabien Thomas wrote: > The purpose of this new build is to report the reproducibility status of > all meta-openembedded recipes. It use the same reproducible selftest than > OE-Core but setting only world as target, and excluding all oecore recipes > from it.

[yocto] [yocto-autobuilder2] [PATCH 4/4] Drop wikilog plugin, we're not going back to it!

Signed-off-by: Richard Purdie --- README.md| 17 +- TODO | 2 - lib/__init__.py | 0 lib/wiki.py | 210 - reporters/wikilog.py | 361 --- services.py | 6 - 6 files changed

[yocto] [yocto-autobuilder2] [PATCH 3/4] services: Update email notification config

Signed-off-by: Richard Purdie --- services.py | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/services.py b/services.py index cc891434..bdfdbc1d 100644 --- a/services.py +++ b/services.py @@ -3,20 +3,27 @@ # from buildbot.plugins import

[yocto] [yocto-autobuilder2] [PATCH 2/4] config.py: Add mickledore prev_release documentation on workers

Signed-off-by: Richard Purdie --- config.py | 1 + 1 file changed, 1 insertion(+) diff --git a/config.py b/config.py index 68c690cc..cc44ec3d 100644 --- a/config.py +++ b/config.py @@ -160,6 +160,7 @@ all_workers = workers + workers_bringup + workers_buildperf + workers_arm # Worker

[yocto] [yocto-autobuilder2] [PATCH 1/4] config.py: Update perf workers to match autobuilder

Signed-off-by: Richard Purdie --- config.py | 9 + schedulers.py | 6 ++ 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/config.py b/config.py index a9433be5..68c690cc 100644 --- a/config.py +++ b/config.py @@ -109,7 +109,7 @@ trigger_builders_wait_full_releases

[yocto] [yocto-autobuilder2] [PATCH] builders: Switch to new qa email scripts name, force updates to helper instead

Signed-off-by: Richard Purdie --- builders.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builders.py b/builders.py index 70b2d066..539b7b4e 100644 --- a/builders.py +++ b/builders.py @@ -328,7 +328,7 @@ def create_parent_builder_factory(buildername, waitname

Re: [yocto] Trouble enabling vtable-verify for gcc-cross

On Wed, 2023-09-27 at 09:40 -0500, Alex Roberts wrote: > Hello All, > > I'm having trouble getting gcc-cross-9.3.0 recipe to build libvtv. I > have added “—enable-vtable-verify” to EXTRA_OECONF via a .bbappend. > The vtable stubs are added to libstdc++ but libvtv itself is not > compiled. This

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M3.rc9)

On Tue, 2023-09-26 at 21:01 +, Pokybuild User wrote: > A build flagged for QA (yocto-4.3_M3.rc9) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.3_M3.rc9 > > > Build URL: >

Re: [yocto] [yocto-autobuilder-helper] [PATCH] scripts/send-qa-email: Add URL of build to QA email

On Tue, 2023-09-26 at 12:03 +0100, Richard Purdie via lists.yoctoproject.org wrote: > Signed-off-by: Richard Purdie > --- > scripts/send_qa_email.py | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/scripts/send_qa_email.py b/scripts/send_qa_email.

[yocto] [yocto-autobuilder-helper] [PATCH] scripts/send-qa-email: Add URL of build to QA email

Signed-off-by: Richard Purdie --- scripts/send_qa_email.py | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/scripts/send_qa_email.py b/scripts/send_qa_email.py index d113377..3d02797 100755 --- a/scripts/send_qa_email.py +++ b/scripts/send_qa_email.py @@ -101,6 +101,9

[yocto] [yocto-autobuilder-helper] [PATCH] qa_email: Ensure we set an error exit code for errors

Whilst the script needs to continue if we fail to generate a regression report, set the exit code accordingly so our CI can flag the issue. Signed-off-by: Richard Purdie --- scripts/send_qa_email.py | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/scripts

[yocto] [yocto-autobuilder-helper] [PATCH] qa_email: Add headers to the script to improve debugging

It is hard to tell which section of the code specific error messages come from at present. Add more headers to the output so we can at least tell which section the messages are from. It also adds some timing information. Signed-off-by: Richard Purdie --- scripts/send_qa_email.py | 7 +++ 1

Re: [yocto] [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

On Fri, 2023-09-22 at 11:17 +0200, Alexander Kanavin wrote: > On Thu, 21 Sept 2023 at 16:39, chris.lapla...@agilent.com > wrote: > > > That is very impressive and I'd also love to hear about what heuristics it > > uses. > > It's actually rather simple. It uses glob.glob on stamps in tmp/, then

Re: [yocto] Forcing uninative?

On Wed, 2023-09-20 at 14:39 -0700, Rudolf J Streif wrote: > Thank you, Alexandre. > > On 9/20/23 14:16, Alexandre Belloni wrote: > > Hello, > > > > On 20/09/2023 13:59:54-0700, Rudolf J Streif wrote: > > > I need to resurrect a Yocto Project build environment based on honister. > > > My > > >

Re: [yocto] [RFC] recipetool create to support pypi project

On Wed, 2023-09-20 at 18:48 +0200, Julien Stephan wrote: > Hi all, > > In the scope of the RFQ, I am currently looking at bug #14737 (adding > support of PEP-517 in recipetool/devtool). > > I am quite new to the recipetool/devtool tools and I have several > ideas I would like to discuss before

Re: [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

On Thu, 2023-09-14 at 20:51 +0200, Alexander Kanavin wrote: > On Thu, 14 Sept 2023 at 14:56, Richard Purdie > wrote: > > For the task signatures, we need to think about some questions. If I > > make a change locally, can I query how much will rebuild and how much

Re: [yocto] Errno=No space left on device

On Thu, 2023-09-14 at 12:35 +, Dave Hitchman wrote: > > Does anyone know what IS enough? Watching the video series > around https://www.youtube.com/watch?v=bTEdfwtPtNY he doesnt mention > changing this size. I dont actually know what this watch manager > thing is supposed to be doing, there

Re: [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

On Thu, 2023-09-14 at 13:52 +0200, Alexander Kanavin wrote: > On Tue, 12 Sept 2023 at 16:44, Stephen Jolley wrote: > > Alexander Kanavin will be working on the core workflow topic > > I am now ready to start doing this, but before I do, I'd like to > decompose the subject into manageable tasks

[yocto] [yocto-autobuilder-helper] [PATCH 5/5] config.json: Drop most core-image-minimal-dev image tests and add core-image-full-cmdline

Signed-off-by: Richard Purdie --- config.json | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/config.json b/config.json index 685e957..59944f2 100644 --- a/config.json +++ b/config.json @@ -86,7 +86,7 @@ ], "

[yocto] [yocto-autobuilder-helper] [PATCH 3/5] config.json: Drop now unneeded SDKMACHINE settings

Signed-off-by: Richard Purdie --- config.json | 28 1 file changed, 28 deletions(-) diff --git a/config.json b/config.json index df83bdb..bc73e93 100644 --- a/config.json +++ b/config.json @@ -102,7 +102,6 @@ "IMAGE_INSTALL:append = ' ssh-p

[yocto] [yocto-autobuilder-helper] [PATCH 4/5] config.json: Consolodate oecore test steps

Signed-off-by: Richard Purdie --- config.json | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/config.json b/config.json index bc73e93..685e957 100644 --- a/config.json +++ b/config.json @@ -319,17 +319,13 @@ "BB_SIGNATURE_HANDLER = 'OEEqui

[yocto] [yocto-autobuilder-helper] [PATCH 2/5] config.json: Prefer x86_64 SDKMACHINE to i686

The i686 SDKMACHINE target makes little sense now, reduce it's usage substantially to match use in reality and make x86_64 the default. Signed-off-by: Richard Purdie --- config.json | 49 + 1 file changed, 25 insertions(+), 24 deletions(-) diff

[yocto] [yocto-autobuilder-helper] [PATCH 1/5] config.json: Set SDKMACHINE explicitly

SDKMACHINE defaults to i686 for historical reasons but it should no longer be the main thing we test. Start to improve things by setting things by everywhere explicitly so we can then rationalise to what makes sense. Signed-off-by: Richard Purdie --- config.json | 10 ++ 1 file

[yocto] [yocto-autobuilder-helper] [PATCH] config.json: Reduce testing on qemumips/qemumips64/qemuppc

Introduce the concept of "qemu lite" and reduce the testing on these platforms, mainly with the removal of core-imaege-sato-sdk. Signed-off-by: Richard Purdie --- config.json | 34 -- 1 file changed, 28 insertions(+), 6 deletions(-) diff --git a/con

Re: [yocto] SDK build generally broken?

> > Thanks for any help! > Greets > > Am Montag, dem 21.08.2023 um 23:53 +0100 schrieb Richard Purdie: > > On Mon, 2023-08-21 at 12:49 +, David Daniel wrote: > > > Hello everybody > > > > > > Has anyone successfully built an SDK l

Re: [yocto] SDK build generally broken?

On Mon, 2023-08-21 at 12:49 +, David Daniel wrote: > Hello everybody > > Has anyone successfully built an SDK lately? I cannot build any SDK, > neither for my image nor for core-image-minimal. > > If I define my own image I get the error (I already wrote - nobody any > idea?) that the

Re: [yocto] [OE-core] Yocto Project Status 15 August 2023 (WW33)

On Tue, 2023-08-15 at 21:13 +0200, Alexander Kanavin wrote: > On Tue, 15 Aug 2023 at 16:52, Stephen Jolley wrote: > > The various systemd issues have mostly been resolved although the AUH did > > break as a result and will have to be fixed and rerun. > > I sent the patch now - it's for

Re: [yocto] Intermittent build failure where dwarfsrcfiles doesn't exist

On Sat, 2023-08-12 at 07:50 +1200, Tom Isaacson wrote: > My bad. Ok, so: > * What function is responsible for copying the dwarfsrcfiles binary to > poky/build/tmp/work/oclea_cv25-oclea-linux/my-app/1.0.53-8c74bcd/recipe-sysroot-native/usr/bin/dwarfsrcfiles? It would come from the

Re: [yocto] Intermittent build failure where dwarfsrcfiles doesn't exist

On Fri, 2023-08-11 at 09:22 +1200, Tom Isaacson wrote: > DEBUG: Checking >

Re: [yocto] sstate-cache miss analyzation

On Wed, 2023-08-09 at 13:31 -0600, Rusty Howell wrote: > Hi, I was reading this very old mailing list post about SSTATE and > cache hits. > > https://www.openembedded.org/pipermail/openembedded-core/2014-June/211563.html > > Is the information in that message still accurate?  Are there any >

Re: [yocto] Intermittent build failure where dwarfsrcfiles doesn't exist

On Tue, 2023-08-08 at 18:10 +1200, Tom Isaacson wrote: > We've been using Dunfell for a while but recently I've started getting > an intermittent build failure from an app: > ERROR: my-app-1.0.52-213f116 do_package: Fatal errors occurred in > subprocesses: > [Errno 2] No such file or

Re: [yocto] Questions on multiconfig

On Sat, 2023-08-05 at 16:04 +0200, Stéphane Veyret wrote: > > First of all, I am spammed with messages like: > > > > NOTE: Deferred task > > mc:initramfs:/home/stephane/Developpements/yocto/sources/poky/meta/ > > recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_package_qa now > > buildable > >

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.27.rc2)

On Sat, 2023-08-05 at 03:06 +, Pokybuild User wrote: > A build flagged for QA (yocto-3.1.27.rc2) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.1.27.rc2 > > > Build hash information: > > bitbake:

Re: [yocto] [docs] Updating the list of sanity tested distros?

On Fri, 2023-07-28 at 20:41 +0200, Michael Opdenacker via lists.yoctoproject.org wrote: > Greetings, > > As far as I understand, the list of distros that the Yocto Project > supports (or should claim it supports) is the intersection of the list > of sanity tested distros (SANITY_TESTED_DISTROS

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M2.rc2)

On Thu, 2023-07-27 at 12:01 +0100, Richard Purdie via lists.yoctoproject.org wrote: > On Thu, 2023-07-27 at 10:53 +0100, Richard Purdie via > lists.yoctoproject.org wrote: > > On Thu, 2023-07-27 at 00:39 +, Pokybuild User wrote: > > > A build flagged for QA (yocto-4.3_

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M2.rc2)

On Thu, 2023-07-27 at 10:53 +0100, Richard Purdie via lists.yoctoproject.org wrote: > On Thu, 2023-07-27 at 00:39 +, Pokybuild User wrote: > > A build flagged for QA (yocto-4.3_M2.rc2) was completed on the > > autobuilder and is available at: > > &

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M2.rc2)

On Thu, 2023-07-27 at 00:39 +, Pokybuild User wrote: > A build flagged for QA (yocto-4.3_M2.rc2) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.3_M2.rc2 > > > Build hash information: > > bitbake:

Re: [yocto] File magic/sdk relocation

On Sun, 2023-07-23 at 14:03 +0200, Alexander Kanavin wrote: > On Fri, 21 Jul 2023 at 19:11, Oleksandr Hnatiuk via > lists.yoctoproject.org > wrote: > > > > On Mon, Jun 19, 2023 at 08:27 PM, Alexander Kanavin wrote: > > > > On closer look, it should even say: > > export

[yocto] Test regression report for 4.2 M2

Hi, We have the 4.3 M2 build so I was curious how the regression report looked this time: https://autobuilder.yocto.io/pub/releases/yocto-4.3_M2.rc1/testresults/testresult-regressions-report.txt The good news is I think this is improving and we're getting there, this one does have useful data

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M2.rc1)

On Thu, 2023-07-20 at 10:54 +, Pokybuild User wrote: > A build flagged for QA (yocto-4.3_M2.rc1) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.3_M2.rc1 > > > Build hash information: > > bitbake:

Re: [yocto] Request for Quotations for development work

On Tue, 2023-07-18 at 09:00 +1200, Tom Isaacson wrote: > I read this and the linked articles and one piece in > https://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/ > caught my eye: > > One question that comes up

Re: [yocto] Request for Quotations for development work

On Tue, 2023-06-20 at 15:09 +0100, Richard Purdie via lists.yoctoproject.org wrote: > The project has some exciting plans in progress and I'm happy to say > we're now in the fortunate position that we're able to seek quotations > for some development work. For more details please see

Re: [yocto] [meta-security][PATCH] layer: add more memory for Qemu machines

On Thu, 2023-06-29 at 13:45 +0300, Mikko Rapeli wrote: > Hi, > > On Wed, Jun 28, 2023 at 05:47:21PM +0100, Richard Purdie wrote: > > On Wed, 2023-06-28 at 08:56 -0400, Armin Kuster wrote: > > > Signed-off-by: Armin Kuster > > > --- > > > conf/l

Re: [yocto] report one objcopy bug and fix

On Wed, 2023-06-28 at 19:48 -0700, cdd...@ambarella.com wrote: > Hi Richard, >     the tar version is >  tar --version > tar (GNU tar) 1.30 > Copyright (C) 2017 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > . > This is free

Re: [yocto] report one objcopy bug and fix

On Wed, 2023-06-28 at 00:55 -0700, cdd...@ambarella.com wrote: > Hi, >     A bug is triggered when using docker + Ubuntu 20.04.3 LTS. The > bug message is : > > File: 'xxx/build/poky/meta/classes/kernel-module-split.bbclass', > lineno: 68, function: extract_modinfo > 0064:   

Re: [yocto] [meta-security][PATCH] layer: add more memory for Qemu machines

On Wed, 2023-06-28 at 08:56 -0400, Armin Kuster wrote: > Signed-off-by: Armin Kuster > --- > conf/layer.conf | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/conf/layer.conf b/conf/layer.conf > index 334a945..5f289cb 100644 > --- a/conf/layer.conf > +++ b/conf/layer.conf > @@ -28,4

Re: [yocto] python3-speechrecognition building using yocto recipe #yocto

On Wed, 2023-06-21 at 04:10 -0700, lavkhush2...@gmail.com wrote: > Hi all,  > > I want to create .deb file of package python3-speechrecognition  , I  > successfully builded natively on target board riscv platform and i > copied binary from target board and with using  recipe i am copying > binary

[yocto] Request for Quotations for development work

Hi All, The project has some exciting plans in progress and I'm happy to say we're now in the fortunate position that we're able to seek quotations for some development work. For more details please see this page on website:

[yocto] [ptest-runner2] [PATCH] utils: Ensure data is only written with a mutex held

Signed-off-by: Richard Purdie --- utils.c | 25 + 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/utils.c b/utils.c index ec57fa4..65b1df3 100644 --- a/utils.c +++ b/utils.c @@ -63,6 +63,7 @@ static struct { int timeouted; pid_t pid; in

Re: [yocto] Going on supporting Ubuntu 18.04?

On Mon, 2023-06-19 at 09:53 +, Ross Burton wrote: > On 19 Jun 2023, at 10:48, Alex Kiernan via lists.yoctoproject.org > wrote: > > FWIW we swapped out our x86_64 build machines for Aarch64 build > > machines (both 20.04) in AWS with pretty much zero pain - it went way > > better than I was

Re: [yocto] Going on supporting Ubuntu 18.04?

On Mon, 2023-06-19 at 09:44 +, Ross Burton wrote: > On 19 Jun 2023, at 10:34, Richard Purdie via lists.yoctoproject.org > wrote: > > The ARM worker worries me a lot more. The 1804 worker is currently > > stable but I do worry a bit what will happen when we change the OS o

Re: [yocto] Going on supporting Ubuntu 18.04?

On Mon, 2023-06-19 at 11:02 +0200, Alexander Kanavin wrote: > Even if we would have a subscription with Canonical, it would not be > fair to ask contributors to fix issues that occur only on distribution > available through commercial channels. So yes, it should be dropped > ASAP. > > Alex > >

[yocto] [ptest-runner2] [PATCH] utils: Ensure buffers are flushed after child exits

are in sync. This does appear to improve warnings on the autobuilder now we started detecting the issue. Signed-off-by: Richard Purdie --- README.md | 2 +- utils.c | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 85ef58a..e6f548e 100644 --- a/README.md

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On Fri, 2023-06-16 at 16:58 +0200, Alexis Lothoré wrote: > On 6/15/23 22:34, Alexis Lothoré wrote: > > Hello Richard, Michael, > > On 6/15/23 15:41, Richard Purdie wrote: > > > On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via > > > lists.yoctoproject.org wr

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via lists.yoctoproject.org wrote: > From: Alexis Lothoré > > This series is a follow-up for the 4.3_M1.rc1 regression report issue. > > It has been observed that the report is empty. This issue is linked to > configuration description in

Re: [yocto] [yocto-autobuilder-helper][PATCH] ab-janitor: only rm trashdir files over 60s old

On Tue, 2023-06-13 at 13:05 -0400, Trevor Gamblin wrote: > [YOCTO #14952] -- https://bugzilla.yoctoproject.org/show_bug.cgi?id=14952 > > Help avoid contention by adding a check to ensure files and directories > are at least 60s old when attempting to delete them from the trashdir, > in case

Re: [yocto] #fakeroot #pseudo-native #xattr #attr-native #yocto

On Wed, 2023-06-14 at 08:48 -0700, jbarnesweb via lists.yoctoproject.org wrote: > Thanks for your reply, Richard. > > The  task was elided above. Here's what the recipe looks like now. (I removed > the fakeroot decorator from the function signature). It still stops with > Operation not

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On Wed, 2023-06-14 at 16:29 +0200, Alexandre Belloni wrote: > On 14/06/2023 14:15:54+0200, Alexis Lothoré wrote: > > On 6/14/23 12:31, Richard Purdie wrote: > > > On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via > > > lists.yoctoproject.org wrote: &

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/3] fix test results storage for mickledore

On Wed, 2023-06-14 at 10:56 +0200, Alexis Lothoré via lists.yoctoproject.org wrote: > From: Alexis Lothoré > > This series is a follow-up for the 4.3_M1.rc1 regression report issue. > > It has been observed that the report is empty. This issue is linked to > configuration description in

Re: [yocto] #fakeroot #pseudo-native #xattr #attr-native #yocto

On Tue, 2023-06-13 at 10:55 -0700, jbarnesweb via lists.yoctoproject.org wrote: > I'm trying to understand why I get an Operation not permitted error (errno > EPERM) with a fakeroot function that calls setfattr. > Using yocto packages pseudo-native/attr-native >   > In my recipe, this function is

Re: [yocto] [yocto-autobuilder-helper][PATCH] clobberdir: only move dirs more than 60s old

On Wed, 2023-06-07 at 15:41 -0400, Trevor Gamblin wrote: > See: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14952 > > Help avoid contention by adding a check to ensure targets are at > least 60s old when attempting to move them into a trash directory. > > Signed-off-by: Trevor Gamblin >

Re: [yocto] sstate-cache issue with SPDX enabled

On Wed, 2023-06-07 at 08:32 -0700, m...@ambarella.com wrote: > We’re using Poky Kirkstone(LTS) with the latest version for our > SDK. Recently, we're trying to enable the feature of creating SBOM in > SPDX. But we met a sstate-cache checking failure issue when enabling > SPDX to generate SBOM. It

Re: [yocto] [meta-mingw] [PATCH] Ignore WINDRES from hash

On Thu, 2023-06-08 at 07:03 +, Samuli Piippo wrote: > Amend 6badedaa3e4df5b00b5aa992c5c174e315b09972 and add WINDRES > to be ignored from hash, otherwise it contaminates sstate cache > for every recipe. > > Signed-off-by: Samuli Piippo > --- > conf/machine-sdk/include/mingw32-common.inc | 2

Re: [yocto] Register out-of-tree fetcher with devtool

On Fri, 2023-06-02 at 04:47 +, Weihmann, Konrad (Avnet Embedded) wrote: > > > > Hi all, >   > we do have an out-of-tree fetcher that I would like to make use of > with devtool, for instance for upgrade checking. > Within our recipes the fetcher is registered by this workaround > > python

Re: [yocto] #Yocto #GitHub mirror - tags

On Fri, 2023-06-02 at 01:03 -0700, Nemo wrote: > Hi, > I was using the GitHub mirrorfor shallow clones, and noticed that > while its syncing commits, the tags aren't being pushed there. > The last sync with tags happened in February, so its missing all tags > since. I've been trying to get this

Re: [yocto] libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by bin/cmake) #hardknott

On Wed, 2023-05-24 at 05:04 -0700, Mahendra Sondagar wrote: > Hi.. community  > Hope all are doing well  >   > I'm dealing with the Yocto hardknott with my Ubuntu host  > The Ubuntu version is Ubuntu 22.04.2 LTS >   > During the building of the custom image, everything goes well until > the build

Re: [yocto] [meta-darwin][PATCH 1/2] Add new maintainers

dex a58ab39..e4ac9bc 100644 > --- a/README > +++ b/README > @@ -48,7 +48,10 @@ This layer depends on: > layers: meta-clang > branch: kirkstone > > -Layer Maintainer: Richard Purdie > +Layer Maintainers: Richard Purdie > + Dominik Schnitzer >

Re: [qa-build-notification] [yocto] QA notification for completed autobuilder build (yocto-3.1.25.rc1)

On Thu, 2023-05-11 at 03:38 +, Jing Hui Tham wrote: > Hi All, > > QA for yocto-3.1.25.rc1 is completed. This is the full report for this > release: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults > > === Summary > No

Re: [qa-build-notification] [yocto] QA notification for completed autobuilder build (yocto-4.1.4.rc1)

On Mon, 2023-05-08 at 02:55 +, Jing Hui Tham wrote: > Hi All, > > QA for yocto-4.1.4.rc1 is completed. This is the full report for this > release: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults > > === Summary > No

Re: [yocto] Yocto Project Community Manager updates

On Thu, 2023-05-04 at 16:40 +0200, Nicolas Dechesne wrote: > After five years, I have decided to resign from my position as the > Yocto Project Community Manager. I joined the OpenEmbedded community > around 2008. I have fond memories of my early days, and still > remember some of my first

[yocto] 4.2 release going to rc3

Hi, Whilst we had a green QA report and were thinking rc2 would release, we did get a user report of problems with graphics on qemu and sato was inoperable (bug 15100). Sadly our QA automation doesn't catch an issue like this and it mustn't have shown on real hardware. Due to the nature of the

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2.rc1)

ssage- > > From: qa-build-notificat...@lists.yoctoproject.org > notificat...@lists.yoctoproject.org> On Behalf Of Richard Purdie > > Sent: Thursday, April 6, 2023 3:57 PM > > To: > > Cc: qa-build-notification > > Subject: [qa-build-notification] QA notification

[yocto] QA notification for completed autobuilder build (yocto-4.2.rc1)

A build flagged for QA (yocto-4.2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.2.rc1 Build hash information: bitbake: 46e1ea2e9a203992bb4de48ea21a8e736419ada2 meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0 meta-arm:

Re: [yocto] [yocto-autobuilder-helper][PATCH 2/2] scripts/generate-testresult-index.py: expose regression reports on web page

On Fri, 2023-03-24 at 10:00 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > From: Alexis Lothoré > > When available, expose tesresult-regressions-report.txt on non-release web > page, > as it is done for many other artifacts currently > > Signed-off-by: Alexis Lothoré > --- >

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/8] fix regression reports generation on "master-next" branches

On Mon, 2023-03-13 at 15:51 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > From: Alexis Lothoré > > This series fixes regression report generation on "next" branches, as raised > in > [1]. > > The first five patches are preparatory updates for the real fix, being either >

Re: [linux-yocto] [kernel-cache][PATCH 08/11] bsp/intel-corei7-64-preempt-rt: Add support for Time-Sensitive Network

On Tue, 2023-03-07 at 21:12 +0100, Alexander Kanavin wrote: > On Tue, 7 Mar 2023 at 19:23, Paul Gortmaker > wrote: > > I won't repeat what others have already said, but just to be clear, the > > kernel config for a platform is 100% independent from having "a rich > > command line experience" > >

Re: [linux-yocto] [kernel-cache][PATCH 08/11] bsp/intel-corei7-64-preempt-rt: Add support for Time-Sensitive Network

On Tue, 2023-03-07 at 16:30 +0100, Alexander Kanavin wrote: > On Tue, 7 Mar 2023 at 15:58, Paul Gortmaker > wrote: > > Unfortunately, not everything is a module. As to your "so what if the > > existing machines enable everything under the sun and install it onto > > the image" -- well obviously

Re: [yocto] Question about psuedo abort errors

I saw you're still having problems even with the latest pseudo revisions. I'll make some comments below. On Thu, 2023-02-23 at 02:27 -0800, Tamis wrote: > Install error: > > + install -m 0644 >

Re: [yocto] Question about psuedo abort errors

Hi, On Thu, 2023-02-23 at 02:27 -0800, Tamis wrote: > I know that this might be an old thread but we seem to deal the exact > same issue in our yocto builds, that's why I am writing here. > Recently we switched from sumo yocto branch to dunfel. > Now some recipes with nothing special in it, just

Re: [yocto] AlmaLinux 8.5 support in Langdale

On Mon, 2023-02-20 at 13:09 +, Chaplin, Kris via lists.yoctoproject.org wrote: > Thanks Alex, > > > Note that the list of supported host distros is set only for the poky > > reference distro with a weak assignment, and not for oe-core or yocto > > as a whole. If you do your own tests, and

Re: [yocto] AlmaLinux 8.5 support in Langdale

On Mon, 2023-02-20 at 09:12 +, Chaplin, Kris via lists.yoctoproject.org wrote: > Hello, > > I'm working with our team to test supported development OS for our > AMD/Xilinx PetaLinux distribution built on top of Langdale. The official > supported Linux distributions are Ubuntu, Fedora,

Re: [yocto] [meta-oe][dunfell]nativesdk-postgresql - causing chown: invalid user: 'postgres:postgres'

On Thu, 2023-02-09 at 23:16 -0800, alexander.roda...@brose.com wrote: > I integrated the changes of the commit you posted, however i still > have the same error message coming up. Do i need to make changes in > the recipe to make the  intercept work? No, it should have changed PATH in the recipe

Re: [yocto] [meta-oe][dunfell]nativesdk-postgresql - causing chown: invalid user: 'postgres:postgres'

On Thu, 2023-02-09 at 00:05 -0800, alexander.roda...@brose.com wrote: > Hello, > > i am trying to install the PostgreSQL and the development package > (postgresql-server-dev) as part of the SDK.  > > I added via bbappend BBCLASSEXTED_append = "nativesdk" to the > postgresql_12.9.bb.  > > I can

Re: [yocto] [autobuilder][PATCH 0/3] ease send-qa-email usage with older history

On Tue, 2023-02-07 at 15:52 +0100, Alexis Lothoré wrote: > Hello Richard, > > On 2/7/23 15:42, Richard Purdie wrote: > > On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via > > lists.yoctoproject.org wrote: > > > I assumed that no tool is currently trying to parse

Re: [yocto] [autobuilder][PATCH 0/3] ease send-qa-email usage with older history

On Tue, 2023-02-07 at 15:12 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > Hello, > this minor patch series bring minor fixes into send-qa-email to ease > development/debugging in it: > - fetching current build test results works well in CI builds because we are > sure that the build

Re: [yocto] error when try to use sudo command in recipe

On Sun, 2023-02-05 at 16:00 -0800, SIMON BABY wrote: > Hi Richard, > > I added extra code in the recipe to print the sudo permissions to > compare with actual permissions. I'll ask for the third time. Are you running bitbake directly? I'd like to understand the environment bitbake is being run

Re: [yocto] error when try to use sudo command in recipe

On Sun, 2023-02-05 at 08:44 -0800, SIMON BABY wrote: > On Sun, Feb 5, 2023 at 01:54 AM, Richard Purdie wrote: > > something > Hello Richard, > I am building this layer for adding container images into the root > file system and load on the target as part of the image download.

Re: [yocto] error when try to use sudo command in recipe

On Sat, 2023-02-04 at 20:15 -0800, SIMON BABY wrote: > Hi Richard, > Thank you for the reply. >  I was trying to add the > layer https://github.com/savoirfairelinux/meta-embedded-containers in > my yocto build. Below recipe uses sudo commands.  > >

Re: [yocto] error when try to use sudo command in recipe

On Fri, 2023-02-03 at 14:08 -0800, SIMON BABY wrote: > Hello team, > I am getting the below error whe try to execute command in bitbake > recipe having sudo. eg: sudo kill > > sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit > set > > Can some please help how to fix it. The

Re: [yocto] Questions about some functions

On Thu, 2023-02-02 at 06:57 +, wangmy wrote: > I see the following two items on the page of 2022 Yocto Project Weekly Status > Archive: > 1. A tool, used for collaboration on the creation of release notes, > git-refinery-web has been made publicly available by Intel, thanks! > We may not be

Re: [yocto] [PATCH] samhain: rework due to changed oe cache handling

On Fri, 2023-01-27 at 13:30 +0100, Max Krummenacher wrote: > From: Max Krummenacher > > OE-Core changed the cache handling which made the use of ${BPN} fail. > > > Parsing recipes...WARNING: .../samhain-standalone.bb: Exception during > > build_dependencies for do_configure > > WARNING:

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2_M2.rc2)

On Fri, 2023-01-27 at 05:13 +, Pokybuild User wrote: > A build flagged for QA (yocto-4.2_M2.rc2) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.2_M2.rc2 > > > Build hash information: > > bitbake:

Re: [yocto] [autobuilder][PATCH v3 0/5] generate regression reports against proper releases

On Fri, 2023-01-27 at 09:26 +0100, Alexis Lothoré wrote: > On 1/26/23 23:42, Richard Purdie wrote: > > On Tue, 2023-01-24 at 18:30 +0100, Alexis Lothoré via > > lists.yoctoproject.org wrote: > > > > > Thanks. Since I like living dangerously, I've put these on th

Re: [yocto] [autobuilder][PATCH v3 3/5] scripts/send-qa-email: Generate regression reports against most relevant release

On Tue, 2023-01-24 at 18:30 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > Instead of only generating regressions reports against HEAD of relevant > branch, compute > most relevant tag (ie : release) against which we can check for regressions. > General rules > introduced are the

Re: [yocto] [autobuilder][PATCH v3 0/5] generate regression reports against proper releases

On Tue, 2023-01-24 at 18:30 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > Hi, this is the 3nd version of work initiated to improve regression reports > usefulness, started around issue YOCTO #1465 > (https://bugzilla.yoctoproject.org/show_bug.cgi?id=14065). > > Changes since v2: > -

Re: [yocto] [autobuilder][PATCH v2 1/1] builders: update send-qa-email name

On Mon, 2023-01-23 at 13:55 +, Richard Purdie via lists.yoctoproject.org wrote: > On Mon, 2023-01-23 at 13:33 +0100, Alexis Lothoré via > lists.yoctoproject.org wrote: > > Signed-off-by: Alexis Lothoré > > --- > > builders.py | 2 +- > > 1 file chang

Re: [yocto] [autobuilder][PATCH v2 1/1] builders: update send-qa-email name

On Mon, 2023-01-23 at 13:33 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > Signed-off-by: Alexis Lothoré > --- > builders.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/builders.py b/builders.py > index d942346..b052f71 100644 > --- a/builders.py > +++

<    1   2   3   4   5   6   7   8   >