golang/go

runtime: TestSignalIgnoreSIGTRAP failures on openbsd

Open

#49,725 opened on Nov 22, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationOS-OpenBSDhelp wanted

Repository metrics

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

Description

greplogs --dashboard -md -l -e '(?ms)FAIL: TestSignalIgnore' --since=2019-11-09

2021-11-18T02:18:12-72f0976/openbsd-amd64-70 2021-11-17T18:14:23-9bdbed1/openbsd-386-68 2021-11-16T15:38:59-7f4a946/openbsd-386-68 2021-11-11T04:41:56-d5a5a13/openbsd-386-68 2021-11-08T22:05:00-67e2294/openbsd-386-68 2021-11-04T21:33:23-71fc881/openbsd-386-68 2021-10-04T15:50:43-9432320/openbsd-386-68 2021-09-17T22:41:29-50e4508/openbsd-arm64-jsing 2021-08-18T08:26:44-8b471db/openbsd-386-68 2021-05-26T22:43:54-1d5298d/openbsd-arm64-jsing 2021-05-26T18:33:56-a92460f/openbsd-arm64-jsing 2021-04-18T17:40:12-4efd581/openbsd-386-68 2021-03-17T07:01:00-72b501c/openbsd-arm-jsing 2021-03-15T19:02:39-2d4042d/openbsd-386-68 2021-03-12T02:21:04-7133096/openbsd-arm64-jsing 2021-02-11T18:04:49-249da7e/openbsd-arm-jsing 2020-12-01T21:41:39-7430266/openbsd-386-68 2020-10-09T13:44:17-51690f7/openbsd-arm-jsing 2020-09-05T14:11:21-bf833ea/openbsd-arm-jsing 2020-03-10T19:41:44-5db3c8f/openbsd-386-64 2020-02-20T14:58:21-24fa159/openbsd-386-62 2020-02-07T23:44:32-a6b03c6/openbsd-amd64-64 2020-02-07T18:08:01-b806182/openbsd-386-62 2019-12-06T23:44:51-94ddb2d/openbsd-386-62

It's not clear to me whether this is related to the other OpenBSD issues (CC @mknyszek @prattmic) or completely independent (CC @4a6f656c).

Given the failure rate at the fact that it seems confined to OpenBSD, perhaps we should add a skip for this test for GOOS=="freebsd"?

Contributor guide

Research direction
Investigate the failing TestSignalIgnoreSIGTRAP test on OpenBSD. Review the test implementation and signal handling code in the Go runtime. Check if there are known differences in SIGTRAP handling on OpenBSD compared to other platforms. Consider whether adding a skip for GOOS=="openbsd" is appropriate, or if a fix can be made to the runtime signal handling.
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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
Gotesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50