golang/go

os/signal: TestTime killed with SIGQUIT on netbsd

Open

#61,303 opened on Jul 11, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationOS-NetBSDcompiler/runtimehelp wanted

Repository metrics

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

Description

#!watchflakes
post <- pkg == "os/signal" && test == "TestTime" && goos == "netbsd" && `SIGQUIT`

Issue created automatically to collect these failures.

Example (log):

SIGQUIT: quit
PC=0x200167e2c m=10 sigcode=0

r0      0x4
r1      0x0
r2      0x0
r3      0x0
r4      0x400003bb40
r5      0x0
r6      0x4000122820
...

runtime.gopark(0x4000032e68?, 0x200104d98?, 0x78?, 0x2e?, 0x20010ca8c?)
	/var/gobuilder/buildlet/go/src/runtime/proc.go:363 +0xe4 fp=0x4000032df0 sp=0x4000032dd0 pc=0x200137e84
runtime.chanrecv(0x40001921e0, 0x0, 0x1)
	/var/gobuilder/buildlet/go/src/runtime/chan.go:583 +0x47c fp=0x4000032e80 sp=0x4000032df0 pc=0x20010608c
runtime.chanrecv1(0x4000192180?, 0x37768e5f1?)
	/var/gobuilder/buildlet/go/src/runtime/chan.go:442 +0x14 fp=0x4000032eb0 sp=0x4000032e80 pc=0x200105bd4
os/signal.TestTime(0x4000184680?)
	/var/gobuilder/buildlet/go/src/os/signal/signal_test.go:689 +0x21c fp=0x4000032f60 sp=0x4000032eb0 pc=0x2001ccdbc
testing.tRunner(0x4000184b60, 0x2002404c0)

— watchflakes

Contributor guide

Research direction
Analyze the stack trace showing SIGQUIT during TestTime on netbsd. Check the os/signal test code and the runtime channel receive path to understand why the test hangs or gets killed. Look for platform specific signal handling differences.
Tech stack
go
Domain
backendtesting
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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
Gotestingsignals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40