golang/go

runtime:cpu1: TestSignalM failures

Open

#75123 opened on Aug 23, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
NeedsInvestigationcompiler/runtimehelp wanted

Description

#!watchflakes
default <- pkg == "runtime:cpu1" && test == "TestSignalM"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestSignalM
    crash_unix_test.go:328: signalM signal not received
--- FAIL: TestSignalM (1.07s)

— watchflakes

Contributor guide

Tech stack
go
Domain
testingperformance
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Go runtime knowledgesignal handlingtesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the flaky failure of TestSignalM in runtime/cpu1. The test checks that a signal sent via signalM is received. Review crash unix test.go and the signal handling code in the runtime. Look for race conditions or timing issues. Check the linked log for more details. Consider discussing on the issue for maintainer guidance.