From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "pratik.farkase@ericsson.com" <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v2] go: add ptest support
Date: Mon, 09 Mar 2026 14:43:40 +0100 [thread overview]
Message-ID: <DGYAO253LE4I.2VZQEXWUZ5G5P@bootlin.com> (raw)
In-Reply-To: <GV2P189MB3005CC084E6CC2C59CCBC5FCFE78A@GV2P189MB3005.EURP189.PROD.OUTLOOK.COM>
On Sun Mar 8, 2026 at 5:58 PM CET, Pratik Farkase wrote:
> Hi Mathieu,
>
> Thanks for testing!
>
> Yes, Go ptest requires significant RAM due to on-the-fly compilation during testing.
> On my setup (qemux86-64 with 4GB RAM), tests complete successfully in ~45 minutes.
>
> The minimum RAM requirement appears to be ~2GB. With less RAM, the OOM killer
> terminates compile processes as you've seen.
>
> Options:
> 1. Increase QB_MEM for go-ptest in the recipe
>
> This is similar to other resource-intensive ptests like gcc or llvm.
>
> What would be the preferred approach for OpenEmbedded-Core?
>
> Thanks,
> Pratik
>
Hi Pratik,
I believe increasing QB_MEM is the way to go, but some reviewers might
have a different opinion.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-09 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 11:02 [OE-core][PATCH v1] go: add ptest support Pratik Farkase
2026-03-06 10:23 ` Mathieu Dubois-Briand
2026-03-06 17:24 ` [OE-core][PATCH v2] " Pratik Farkase
2026-03-06 18:55 ` Jose Quaresma
2026-03-08 16:09 ` Mathieu Dubois-Briand
2026-03-08 16:58 ` Pratik Farkase
2026-03-09 13:43 ` Mathieu Dubois-Briand [this message]
2026-03-18 14:03 ` [OE-core][PATCH v3] " Pratik Farkase
2026-03-19 6:57 ` Mathieu Dubois-Briand
2026-04-13 12:04 ` Pratik Farkase
2026-04-13 12:27 ` Marko, Peter
2026-04-13 22:37 ` Pratik Farkase
2026-04-14 10:10 ` Jose Quaresma
2026-04-14 10:32 ` Pratik Farkase
2026-04-13 12:02 ` [OE-core][PATCH v4] " Pratik Farkase
2026-04-13 22:29 ` [OE-core][PATCH v5] " Pratik Farkase
2026-04-14 10:31 ` [OE-core][PATCH v6] " Pratik Farkase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DGYAO253LE4I.2VZQEXWUZ5G5P@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pratik.farkase@ericsson.com \
--cc=pratik.farkase@est.tech \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox