Yes... the primary case where it was biting us was with our testing suite. It was a set of functional tests that had multiple goroutines going. It was somethin

Yes... the primary case where it was biting us was with our testing suite. It was a set of functional tests that had multiple goroutines going. It was something that had always passed and never been an issue on 1.0.3, but started failing 85-90% of the time on Go 1.1 with no code changes. :(