golang/go

runtime: TestCgoCallbackGC failures

Open

#68,800 opened on Aug 9, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationarch-riscvcompiler/runtimehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestCgoCallbackGC
=== PAUSE TestCgoCallbackGC
=== CONT  TestCgoCallbackGC
    crash_cgo_test.go:68: /home/swarming/.swarming/w/ir/x/t/go-build402992713/testprogcgo.exe CgoCallbackGC: signal: aborted
    crash_cgo_test.go:71: expected "OK\n", but got:
        free(): invalid pointer
--- FAIL: TestCgoCallbackGC (0.38s)

— watchflakes

Contributor guide

Research direction
Reproduce the flaky test TestCgoCallbackGC and trace the CGo callback GC path. Look for memory corruption or signal handling issues.
Tech stack
go
Domain
backend
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.
Half day
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
GoCGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20