Date: Sat, 12 Apr 2025 16:35:37 +0000 From: bugzilla-noreply@freebsd.org To: go@FreeBSD.org Subject: [Bug 285963] lang/go* fail to build on the amd64 package builders Message-ID: <bug-285963-42334-EPOwCX0pn7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-285963-42334@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285963 --- Comment #24 from Nuno Subtil <ns87@shadau.com> --- (In reply to Ryan Shaw from comment #23) > Assuming this is the problem Based on subsequent replies to the list, it sounds like there are two problems. The one you linked seems to be sporadic, a subsequent build didn't run into it, but still couldn't build golang: > 142amd64-quarterly 359bbf7fc5af on beefy20 finished with > "done:" status: No crash. > > It built 26082 of 27764 queued packages. So it was an > incremental bulk build. > > It still has a large Skipped figure (1286). Some major > contributions were the failures of: > > go121-1.21.13_5 (skipped 542) > webkit2-gtk_40-2.46.6 (skipped 323) > go123-1.23.7_4 (skipped 100) https://lists.freebsd.org/archives/freebsd-ports/2025-April/007567.html Unless the GOGC patch from comment #11 works out, the best course of action might be to get to a repro on a system that can be used to debug, or at least test workarounds. I haven't been able to reproduce this yet myself, it sounds like it may require a very specific configuration: specific main snapshot + 14.2 jails, maybe some specific hardware as well? -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285963-42334-EPOwCX0pn7>