Some race tests were sensitive to the goroutine scheduling order.
When this changed in commit
e870f06, these tests started to fail.
Fix TestRaceHeapParam by ensuring that the racing goroutine has
run before the test exits. Fix TestRaceRWMutexMultipleReaders by
adding a third reader to ensure that two readers wind up on the
same side of the writer (and race with each other) regardless of
the schedule. Fix TestRaceRange by ensuring that the racing
goroutine runs before the main goroutine exits the loop it races
with.
Change-Id: Iaf002f8730ea42227feaf2f3c51b9a1e57ccffdd
Reviewed-on: https://go-review.googlesource.com/9402
Reviewed-by: Russ Cox <rsc@golang.org>
}
done <- true
}(i)
+ // Ensure the goroutine runs before we continue the loop.
+ runtime.Gosched()
}
for i := 0; i < N; i++ {
<-done
}
func TestRaceHeapParam(t *testing.T) {
+ done := make(chan bool)
x := func() (x int) {
go func() {
x = 42
+ done <- true
}()
return
}()
_ = x
+ <-done
}
func TestNoRaceEmptyStruct(t *testing.T) {
func TestRaceRWMutexMultipleReaders(t *testing.T) {
var mu sync.RWMutex
var x, y int64 = 0, 1
- ch := make(chan bool, 3)
+ ch := make(chan bool, 4)
go func() {
mu.Lock()
defer mu.Unlock()
x = 2
ch <- true
}()
+ // Use three readers so that no matter what order they're
+ // scheduled in, two will be on the same side of the write
+ // lock above.
go func() {
mu.RLock()
y = x + 1
mu.RUnlock()
ch <- true
}()
+ go func() {
+ mu.RLock()
+ y = x + 3
+ mu.RUnlock()
+ ch <- true
+ }()
+ <-ch
<-ch
<-ch
<-ch
func TestNoRaceRWMutexMultipleReaders(t *testing.T) {
var mu sync.RWMutex
x := int64(0)
- ch := make(chan bool, 3)
+ ch := make(chan bool, 4)
go func() {
mu.Lock()
defer mu.Unlock()
mu.RUnlock()
ch <- true
}()
+ go func() {
+ mu.RLock()
+ y := x + 3
+ _ = y
+ mu.RUnlock()
+ ch <- true
+ }()
+ <-ch
<-ch
<-ch
<-ch