golang/go

runtime:cpu2: TestCgoCCodeSIGPROF failures

Open

#75579 opened on Sep 24, 2025

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

Description

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

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestCgoCCodeSIGPROF
=== PAUSE TestCgoCCodeSIGPROF

— 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.
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Go runtime internalsCgosignal handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the root cause of intermittent failures in TestCgoCCodeSIGPROF. Look at the test file in runtime/testdata/testprogcgo/ and related signal handling code. The issue appears to be a race condition involving SIGPROF during Cgo execution. Check recent changes to runtime signal handling and Cgo.