Comment 1:

Labels changed: added priority-soon, go1.2maybe, removed priority-triage.

Comment 2:

What environment are you running in?  Is this from running the test in make.bash?  Is
your system heavily loaded?
On my Ubuntu laptop I'm seeing only
issue1560.go:44: difference in start time for two sleep(1) is 18ms
and the number is never higher than 20 even when I put load on the system.
I'm not sure how it's getting up to 562ms for you.

Comment 3:

I have been running all.bash in a continuous loop for several days with GOGC set to 1. 
This has happened at least 3 times so far.  Here are the relevant lines from my log file
--- FAIL: TestParallelSleep (1.68 seconds)
        issue1560.go:44: difference in start time for two sleep(1) is 683ms
        issue1560.go:48: parallel 1-second sleeps slept for 0.683000 seconds
--- FAIL: TestParallelSleep (1.61 seconds)
        issue1560.go:44: difference in start time for two sleep(1) is 606ms
        issue1560.go:48: parallel 1-second sleeps slept for 0.606000 seconds
--- FAIL: TestParallelSleep (1.56 seconds)
        issue1560.go:44: difference in start time for two sleep(1) is 562ms
        issue1560.go:48: parallel 1-second sleeps slept for 0.562000 seconds

Comment 4:

Carl, what do you get when you run this:
cd $GOROOT/misc/cgo/test
GOGC=1 go test -run TestParallelSleep -v
It would be nice to know what the typical execution is, so that we can see how much of a
slowdown is happening in the cases that time out.
Three failures in 3+ days on a continuous loop is rare enough that I think we can leave
it for after Go 1.2.

Labels changed: removed go1.2maybe.

Comment 5:

Labels changed: added priority-later, removed priority-soon.

Comment 6:

Labels changed: added go1.3maybe.

Comment 7:

Labels changed: added release-none, removed go1.3maybe.

Comment 8:

Labels changed: added repo-main.

Comment 9:

Another one http://build.golang.org/log/bee2f840d3c60e15c1742fdaa30c37990246a4ce
Alex

Last update 2014. Assuming this is no longer an active concern.