From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
<openembedded-core@lists.openembedded.org>
Cc: <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v1] go: add ptest support
Date: Fri, 06 Mar 2026 11:23:08 +0100 [thread overview]
Message-ID: <DGVMIW1FRS05.1F1INJLSVDOEI@bootlin.com> (raw)
In-Reply-To: <20260305110200.17834-1-pratik.farkase@est.tech>
On Thu Mar 5, 2026 at 12:02 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 your patch.
It looks like this is failing QA, when we are building for another
architecture:
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/bitfields.elf4 [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/rnglistx.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/issue57046-clang.elf5 [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/typedef.elf4 [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/line-gcc-dwarf5.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/line-gcc-zstd.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/cycle.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/split.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/line-gcc.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/ranges.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/line-clang-dwarf5.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/line-clang.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/typedef.elf5 [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/cppunsuptypes.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/dwarf/testdata/typedef.elf [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/elf/testdata/go-relocation-test-gcc930-ranges-no-rela-x86-64 [arch]
ERROR: go-1.26.0-r0 do_package_qa: QA Issue: Architecture did not match (x86-64, expected AArch64) in /usr/lib/go/ptest/src/debug/elf/testdata/go-relocation-test-gcc930-ranges-with-rela-x86-64 [arch]
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/3286
https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/3272
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/3328
https://autobuilder.yoctoproject.org/valkyrie/#/builders/65/builds/3289
https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/3136
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-06 10:23 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 [this message]
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
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=DGVMIW1FRS05.1F1INJLSVDOEI@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