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.