misc/cgo/test: TestParallelSleep is still flaky

[bcmills]

2021-04-15T12:38:13-7ad496b/windows-amd64-2012
2021-04-14T00:25:33-8dcc071/linux-ppc64le-buildlet
2020-04-19T03:12:32-a32262d/netbsd-amd64-9_0

--- FAIL: TestParallelSleep (1.57s)
    testx.go:225: difference in start time for two sleep(1) is 562ms
    testx.go:229: parallel 1-second sleeps slept for 0.562000 seconds
FAIL

See previously #6636, #5638, #5480, #4008, #3964.

CC @ianlancetaylor

[ianlancetaylor]

Very odd that this would have suddenly occurred on three different platforms. Assuming that the original bug was not recurred, this is basically testing how long it takes to start a new goroutine. Very hard to believe that it would take half a second when nothing else should be going on.

CC @mknyszek @prattmic

[bcmills]

greplogs --dashboard -md -l -e 'FAIL: TestParallelSleep' --since=2021-04-16

2021-11-04T07:05:31-2622235/windows-amd64-2012
2021-08-26T17:18:58-d6bdae3/windows-amd64-noregabi
2021-08-20T03:25:17-c92c2c9/windows-amd64-2016
2021-05-27T19:55:46-cdcd028/openbsd-arm64-jsing

[bcmills]

One more today. This test failure seems potentially relevant to #44343, too.

greplogs --dashboard -md -l -e 'FAIL: TestParallelSleep' --since=2021-11-05

2022-01-27T21:11:21-f5fe5a4/windows-amd64-2016

[bcmills]

greplogs --dashboard -md -l -e 'FAIL: TestParallelSleep' --since=2022-01-29

2022-03-09T21:31:58-a987aaf/windows-amd64-2016

[bcmills]

Marking as release-blocker for Go 1.19.

(If this isn't a priority to fix for 1.19, we should skip the test so that it doesn't continue to add noise to the builders.)