On Fri, 2023-10-27 at 09:21 +0200, Alexander Kanavin wrote:
> Those tests are currently run as the last step in a-full/a-quick,
> but it's useful to also trigger them separately, after perhaps
> executing other builders that populate the mirrors (such as
> qemux86-64 and such).
>
> Signed-off-by:
Signed-off-by: Alexander Kanavin
---
config.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/config.py b/config.py
index 50945b4..0da4c0a 100644
--- a/config.py
+++ b/config.py
@@ -132,6 +132,7 @@ builders_others = [
"buildperf-alma8",
"reproducible-meta-oe",
"patchtest",
+
Those tests are currently run as the last step in a-full/a-quick,
but it's useful to also trigger them separately, after perhaps
executing other builders that populate the mirrors (such as
qemux86-64 and such).
Signed-off-by: Alexander Kanavin
---
config.json | 8
1 file changed, 8
Thanks, I'm also just now testing the change that also prints what
sstate paths were actually requested when the test fails due to
missing objects.
Alex
On Fri, 27 Oct 2023 at 10:56, Richard Purdie
wrote:
>
> On Fri, 2023-10-27 at 09:21 +0200, Alexander Kanavin wrote:
> > Those tests are
I think RUNTIMETARGET is already set correctly when fortran is correctly
enabled as in:
https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/gcc/gcc-runtime.inc#n45
since 2016:
Please hold off on this version, there is an error in the layers set()
handling. I will send a v2.
On Fri, Oct 27, 2023 at 3:19 PM Tim Orling via lists.yoctoproject.org
wrote:
> This is a handy helper script to query the Buildbot REST API to
> create a list of Yocto Project Compatible 2.0
A build flagged for QA (yocto-3.1.29.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.1.29.rc1
Build URL:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6111
Build hash information:
bitbake:
There is currently a known reproducibility issue with the vim-common
package. In my opinion nothing that should hold up the release.
Details:
It seems that the last sstate build of vim was done on an Ubuntu 22.04
worker and recent changes there seem to result in an occurance of
"charset=cp1251"
This is a handy helper script to query the Buildbot REST API to
create a list of Yocto Project Compatible 2.0 layers, as defined by
successful running of the "check-layers*" jobs.
The script only considers the 'jobs' ("Builders" in Buildbot speak) you
ask it to query.
The script looks at the
CONFIG_DEVMEM was mistakenly not enabled, which defeats
CONFIG_STRICT_DEVMEM and friends, as it completely removes all
/dev/mem support.
Signed-off-by: C. Andy Martin
---
features/security/security.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
10 matches
Mail list logo
