Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Diane, Joshua, MichaelO, Randy, Richard, Stephen, Steve, Tim, Tony, TrevorG ARs: - Tim to talk with Intel team about bug 14491 ([QA 3.4_M

Backport for hardknott since we have been running for ~1 week with this patch in master and the same load limiting may help reduce build failures for hardknott itself as well as when its builds are ru

Backport for gatesgarth since we have been running for ~1 week with this patch in master and the same load limiting may help reduce build failures for gatesgarth itself as well as when its builds are

Backport for dunfell since we have been running for ~1 week with this patch in master and the same load limiting may help reduce build failures for dunfell itself as well as when its builds are runnin

Add "-l 52" to PARALLEL_MAKE in config.json to limit Make and Ninja builds based on the detected system load. With this option added, if either tool has at least one job running and detects that the s

You are right that it's not actually a percentage and is instead tied to the number of cores. I'll correct the patch body to reflect this when I inevitably send a v2. With the latest testing on the AB

I've submitted an initial patch to yocto@.... My short notes to go along with it: MAKE JOBSERVERS, SYSTEM LOADS, AND THE YOCTO AUTOBUILDER INTRO - Yocto Autobuilder has been experie

This adds the "-l" option to PARALLEL_MAKE in config.json with an initial testing value of 100 (100% system load). This option is supported by both Make and Ninja. However, we also require the "--debu

Hi, I've pushed the patch onto my fork of the poky repo at https://github.com/threexc/poky Let me know how your testing turns out - I am still running tests as well, but it would be good to know how o

When I encountered this failure with the patch, it was because the scripts/make-intercept/make script was not marked as executable. However, there was another failure even after that was changed, clai

I have reworked the patch and I'm doing some testing with it right now. Once I have collected some data (and possibly reworked it further, depending on results), perhaps I can have you test it out as

The instructions in README-Guide.md are a good starting point, but there are some additional guidelines in this patch for setting up worker nodes which may be useful to others who want to run their ow

Sending a v2 - adding an extra line or two about starting the worker(s).

The instructions in README-Guide.md are a good starting point, but there are some additional guidelines in this patch for setting up worker nodes which may be useful to others who want to run their ow

You're right, I don't need the others. Fixing this for the next revision. The beginning of README-Guide.md mentions that the user should reference the Yocto Manual for the required packages, so maybe

Signed-off-by: Trevor Gamblin <trevor.gamblin@...> --- README-Guide.md | 94 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) diff --git a/README-Guide.md b/

Any issues with this patch set? Do I need to resend?

Long-overdue patches based on experiences trying to set up an autobuilder instance. I've split it into two patches because the second patch (the one that line wraps the majority of the document) may n