golang/go

runtime:cpu2: TestBigStackCallbackCgo failures

Open

#76513 opened on Nov 27, 2025

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

Description

#!watchflakes
default <- pkg == "runtime:cpu2" && test == "TestBigStackCallbackCgo"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestBigStackCallbackCgo
=== PAUSE TestBigStackCallbackCgo

— 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.
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
GoCgoGo runtime testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the flaky test TestBigStackCallbackCgo in the runtime package. The failure log shows a pause, but no explicit error. Look at the test source in src/runtime/ and examine the Cgo callback stack handling. Check if there are recent changes to the runtime or Cgo that could trigger this flake. Compare with similar issues on the Go issue tracker.