Hello Simone, You can define it either in your image recipe (if you have a custom one), or in conf/local.conf. True, but this is a more generic mechanism that we chose not to repeat for each

Signed-off-by: Trevor Gamblin <trevor.gamblin@...> --- builders.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builders.py b/builders.py index f94d1dd..fc92e36

I added some comments. Cheers, Richard

Modify the builder_bonuses calculation so that it provides variable bonus time based on the builder, rather than a constant value. Signed-off-by: Trevor Gamblin <trevor.gamblin@...> ---

Hi, I'm looking for advice on https://bugzilla.yoctoproject.org/show_bug.cgi?id=14375 Seems like an easy fix but not sure how I should handle it. I'm willing to put in the effort, just need some

We need a way to limit the builds for when a given worker has less than a certain amount of disk space available. This implements a canStartBuild method based on the example in the Buildbot docs

Hello, I am trying to set a default size for the rootfs.jffs2 generated by Yocto. For this purpose, if I am not wrong, this can be done using the IMAGE_ROOTFS_SIZE option. But where  I have to

Signed-off-by: Steve Sakoman <steve@...> --- config.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config.py b/config.py index 3874f04..58418a7 100644 ---

"Patrick Boettcher" <patrick.boettcher@...> wrote: It was a problem of DDR memory configuration and calibration. Hard to track, but once you know it, easy to find and fix. -- Patrick.

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alexandre, Anuj, Armin, Joshua, Kiran, Randy, Richard, Saul, Stephen, Steve, Tim, Trevor ARs: -

It’s also good to post your build configuration that bitbake prints at the beginning of build this could also be other policies like default libc being musl vs glibc is in play etc

The shell the test is run under could make a difference, it is probably supposed to be running under busybox's own sh. I think we put the busybox utils into PATH in the ptest to try and ensure this is

0001-Fix-NULL-pointer-use-in-selinux_restorecon_set_sehandle.patch added in commit d6ff5a0e67af "libselinux: Backport NULL pointer fix from 3.1" fails to apply because there is a extra level in the

commit b2b3ea27e3e3 "e2fsprogs: Superseded by upstream." removed lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch from SRC_URI. It was no longer applied, but the file was not deleted. Do that

An equivalent patch was merged into 1.45.7: commit 7616fd6a599e "create_inode: set xattrs to the root directory as well". The existing one still applies and actualy breaks building because of

meta-selinux fails to build libselinux and e2fsprogs. These patches fix that and then removes the unused e2fsprogs overrides. Jason Andryuk (3): e2fsprogs: Remove

Both releases are missing an important patch that changes the displayed version from dev to the appropriate release number. This is confusing to the user and probably breaks some assumptions in some

honister and 1.52 Bitbake branch were recently released, so let's build those too. Signed-off-by: Quentin Schulz <quentin.schulz@...> --- scripts/run-docs-build | 4 ++-- 1 file

Hi, We are executing busybox pTests and we see that the test case execution stops at md5sum test case. We analyzed and see that the execution gets stuck here at Line no 29. Below are the

Series merged. Thanks.