runtime: short-term time.Sleep sleepers will be caught under long-term sleepers?

[mikioh]

What steps will reproduce the problem?
1. run attached timefor with flags -l and -s
Usage of ./timefor:
  -l=false: run long-term sleeper
  -s=false: use time.Sleep instead of time.After

What is the expected output?
all time.Sleep sleeper goroutines work well

What do you see instead?
all time.Sleep sleeper gorutines stalled

Attachments:

1. timefor.go (908 bytes)

[mikioh]

Comment 1:

I don't have much time to investigate it for now, but a little bit.
- looks like this happens on time.Sleep only, time.After works well (yay)
- so this issue is not a blocker for go 1.1 release (hooray)

[mikioh]

Comment 2:

It's possible to repro this issue on both go1 and go1.1.

[ality]

Comment 3:

This has to with overflow in runtime·tsleep.

Status changed to Duplicate.

Merged into issue #5321.