golang/go

all: flaky failures on openbsd/ppc64

Open

#74187 opened on Jun 14, 2025

View on GitHub
 (202 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
NeedsInvestigationOS-OpenBSDarch-ppc64xcompiler/runtimehelp wanted

Description

#!watchflakes
post <- goos == "openbsd" && goarch == "ppc64"

There have been a number of flaky failures on the openbsd/ppc64 builder lately. Many (but not all) are "resource temporarily unavailable".

Example (log):

=== RUN   TestMachOBuildVersion
=== PAUSE TestMachOBuildVersion
=== CONT  TestMachOBuildVersion
    link_test.go:386: [/home/swarming/.swarming/w/ir/x/w/goroot/bin/go build -ldflags=-linkmode=internal -o /home/swarming/.swarming/w/ir/x/t/TestMachOBuildVersion613685595/001/main /home/swarming/.swarming/w/ir/x/t/TestMachOBuildVersion613685595/001/main.go]: exit status 1:
        internal/bytealg: /home/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/openbsd_ppc64/asm: fork/exec /home/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/openbsd_ppc64/asm: resource temporarily unavailable
--- FAIL: TestMachOBuildVersion (15.67s)

— watchflakes

Contributor guide

Tech stack
go
Domain
backendtestingbuild system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
GotestingOpenBSD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the 'resource temporarily unavailable' errors on the openbsd/ppc64 builder. Examine the TestMachOBuildVersion test in link test.go and the asm tool fork/exec failure. Review the build log linked in the issue for clues. Determine if this is a resource exhaustion issue or a system limit, and check for any recent changes that may have introduced flakiness.