golang/go

runtime: TestFinalizerOrCleanupDeadlock/Finalizer/Panic failures

Open

#79209 opened on May 5, 2026

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

Description

#!watchflakes
default <- pkg == "runtime" && test == "TestFinalizerOrCleanupDeadlock/Finalizer/Panic"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestFinalizerOrCleanupDeadlock/Finalizer/Panic
=== PAUSE TestFinalizerOrCleanupDeadlock/Finalizer/Panic
=== CONT  TestFinalizerOrCleanupDeadlock/Finalizer/Panic
    crash_test.go:1181: /home/swarming/.swarming/w/ir/x/t/go-build393621835/testprog.exe FinalizerDeadlock: exit status 2
    crash_test.go:1184: output does not contain "runtime.runFinalizers()":
        panic: panic
        
        goroutine 1 [running]:
        main.FinalizerOrCleanupDeadlock(0x0)
        	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/finalizer_deadlock.go:48 +0x6ab
        main.init.8.func1()
        	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/finalizer_deadlock.go:18 +0x1e
        main.main()
        	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/main.go:34 +0x14e
        
        goroutine 18 [runnable]:
        	goroutine running on other thread; stack unavailable
--- FAIL: TestFinalizerOrCleanupDeadlock/Finalizer/Panic (0.08s)

— 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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
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.
clear
Prerequisites
Go runtimetest debugginggoroutinesfinalizers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the flaky test TestFinalizerOrCleanupDeadlock/Finalizer/Panic in runtime/testdata/testprog/finalizer deadlock.go. The test expects output containing 'runtime.runFinalizers()' but it panics without that. Look for race conditions or goroutine scheduling issues. Check if the test is correctly detecting finalizer deadlocks under load.