golang/go

runtime: TestNetpollWaiters failures

Open

#76668 opened on Dec 3, 2025

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

Description

#!watchflakes
default <- pkg == "runtime" && test == "TestNetpollWaiters"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestNetpollWaiters
=== PAUSE TestNetpollWaiters
=== CONT  TestNetpollWaiters
    crash_test.go:1152: /opt/golang/swarm/.swarming/w/ir/x/t/go-build930232214/testprognet.exe NetpollWaiters: exit status 1
    crash_test.go:1155: output is not "OK\n"
        2025/12/03 03:21:22 current waiters 1
--- FAIL: TestNetpollWaiters (1.49s)

— watchflakes

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.
5
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go runtime internalsnetpoll mechanismflaky test debugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the test `TestNetpollWaiters` in `crash test.go` (line 1152). The failure indicates that after the test, the number of waiters is 1 instead of 0. Look at the test logic and the netpoll implementation in the runtime package. Check if there is a race condition or a leftover goroutine. Consider reviewing recent changes to netpoll that might have introduced this flake. See also the example log for details.