os/signal: TestSignalTrace is flaky on openbsd/arm64

[4a6f656c]

The os/signal.TestSignalTrace is flaky on openbsd/arm64:

https://build.golang.org/log/5a334b71cd825842917d59f362ca9c211da82ec9

https://build.golang.org/log/2c4c9b74d2a13ab71e0a00d8430fbf367a4a96e1

This appears to be a signal being lost - it's not currently clear when this issue started, or where the problem exists (and it may well be a kernel related issue). The failure can be reproduced by running os/signal.TestSignalTrace in a loop on an Apple M1 or Apple M2. Running another competing workload (such as a build) will speed up the test failure.

This test should be skipped until it can be diagnosed further.

[gabyhelp]

Related Issues

• os/signal: test failures with "signal: interrupt" and no other output #41561 (closed)
• os/signal: TestSignalTrace failures on linux-ppc64* with "timeout … waiting for hangup" #45773 (closed)
• os/signal: TestSignalTrace failures with "timeout after 100ms waiting for hangup" #46736 (closed)
• os/signal: TestAtomicStop fails #21433 (closed)
• runtime: TestSignalIgnoreSIGTRAP failures on openbsd #49725

Related Code Changes

• runtime: skip TestSignalIgnoreSIGTRAP on all OpenBSD builders
• runtime: skip TestSignalIgnoreSIGTRAP on known-flaky OpenBSD builders

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[gopherbot]

Change https://go.dev/cl/630036 mentions this issue: os/signal: skip TestSignalTrace on openbsd/arm64

[dmitshur]

CC @golang/openbsd.