Re: [OE-core][PATCH v2] go: add ptest support

Pratik Farkase
2026-03-08T16:59:04Z

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

________________________________________
From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Sent: Sunday, March 8, 2026 5:09 PM
To: Pratik Farkase; openembedded-core@lists.openembedded.org
Cc: pratik.farkase@ericsson.com
Subject: Re: [OE-core][PATCH v2] go: add ptest support

On Fri Mar 6, 2026 at 6:24 PM CET, Pratik Farkase wrote:
> Add ptest infrastructure to test the Go standard library.
>
> - Run 'go test -short std' via run-ptest script
> - Install source tree and pkg/include headers
> - Create VERSION file for architecture detection
> - Exclude multi-arch binary testdata to avoid QA errors
>
> Test results: 237/253 pass (93.7%) on qemux86-64.
>
> Known issues:
> - debug/elf, debug/pe, debug/plan9obj, internal/xcoff: missing binary testdata
> - time: requires embedded timezone data
> - net/http: requires unstripped go binary
> - testing, go/types: minor edge cases
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---

Hi Pratik,

Thanks for the new version.

On the autobuilder, the OOM killer is triggered on most tests:

[ 314.773868] Tasks state (memory values in pages):
[ 314.774517] [ pid ] uid tgid total_vm rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name
[ 314.780755] [ 138] 0 138 2490 268 235 33 0 49152 0 -1000 udevd
[ 314.782773] [ 322] 0 322 2379 335 250 85 0 53248 0 -1000 sshd
[ 314.801338] [ 328] 0 328 1015 53 0 53 0 40960 0 0 syslogd
[ 314.811001] [ 331] 0 331 1015 53 0 53 0 40960 0 0 klogd
[ 314.819041] [ 337] 0 337 1029 126 64 62 0 36864 0 0 start_getty
[ 314.820980] [ 338] 0 338 1029 126 64 62 0 45056 0 0 start_getty
[ 314.823947] [ 339] 0 339 1015 32 0 32 0 45056 0 0 getty
[ 314.826345] [ 342] 0 342 1072 153 96 57 0 45056 0 0 sh
[ 314.835899] [ 343] 0 343 1015 83 32 51 0 40960 0 0 getty
[ 314.837471] [ 388] 0 388 2619 335 288 47 0 57344 0 0 sshd-session
[ 314.849074] [ 390] 0 390 2684 454 353 101 0 61440 0 0 sshd-session
[ 314.850742] [ 391] 0 391 639 73 0 73 0 40960 0 0 ptest-runner
[ 314.863046] [ 392] 0 392 1028 105 64 41 0 45056 0 0 run-ptest
[ 314.868775] [ 397] 0 397 335448 14669 14640 29 0 245760 0 0 go
[ 314.881173] [ 398] 0 398 1028 97 39 58 0 45056 0 0 run-ptest
[ 314.882869] [ 798] 0 798 371933 60075 60023 20 32 630784 0 0 compile
[ 314.893578] [ 1230] 0 1230 371846 55334 55248 54 32 589824 0 0 compile
[ 314.895156] [ 1381] 0 1381 371669 48968 48879 57 32 540672 0 0 compile
[ 314.904257] [ 1445] 0 1445 371821 50116 50067 17 32 552960 0 0 compile
[ 314.907744] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=compile,pid=798,uid=0
[ 314.910323] Out of memory: Killed process 798 (compile) total-vm:1487732kB, anon-rss:240092kB, file-rss:408kB, shmem-rss:128kB, UID:0 pgtables:616kB oom_score_adj:0

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3229
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3201
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1196

We might need to increase QEMU memory size. Did you had similar issues
on your side?

Thanks,
Mathieu

--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering