golang/go

all: flaky failures on netbsd/arm

Open

#73820 opened on May 21, 2025

View on GitHub
 (623 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
NeedsInvestigationOS-NetBSDarch-armhelp wanted

Description

#!watchflakes
post <- goos == "netbsd" && goarch == "arm"

There seem to be flaky failures on netbsd-arm in various places. Put them in a central place on this issue.

Contributor guide

Tech stack
go
Domain
testing
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.
needs investigation
Prerequisites
Go programming languageUnderstanding of testing infrastructureFamiliarity with cross platform builds
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
This issue aggregates flaky test failures on netbsd/arm. Start by examining the watchflakes command mentioned in the issue body to reproduce the flakes. Look at the CI logs for recent netbsd/arm runs and identify recurring failures. Check comments for any identified root causes or linked PRs. The goal is to isolate a specific flaky test and propose a fix or workaround.