You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
package main
import"fmt"funcmain() {
fmt.Println("hello, race")
}
Compile present using Go 1.4, open the demo, and hit Run repeatedly. Result: "hello, race" displays consistently.
Compile present using Go tip, open the demo, and hit Run repeatedly. Result: "hello, race" displays maybe one time in three, although the program claims to have exited successfully.
This is probably a logical race in present or playground that the scheduler changes have exposed.
This is probably a high priority, in that I wouldn't want any GopherCon presenters to do a last minute present upgrade and have any unpleasant discoveries.
The text was updated successfully, but these errors were encountered:
This doesn't fix the race; doing that would require a bit of a redesign.
Since GopherCon is this week, just put in this stop-gap measure for now.
Update golang/go#11534
Change-Id: Ied6c5dd52778534a7a08b5ba3fa15c0352a65646
Reviewed-on: https://go-review.googlesource.com/11886
Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
race.slide:
race.go:
Compile present using Go 1.4, open the demo, and hit Run repeatedly. Result: "hello, race" displays consistently.
Compile present using Go tip, open the demo, and hit Run repeatedly. Result: "hello, race" displays maybe one time in three, although the program claims to have exited successfully.
This is probably a logical race in present or playground that the scheduler changes have exposed.
This is probably a high priority, in that I wouldn't want any GopherCon presenters to do a last minute
present
upgrade and have any unpleasant discoveries.The text was updated successfully, but these errors were encountered: