Hey Will, it might help to get timings for just -race and -coverprofile (not both) to try to isolate timing increase a bit.
On Mon, Feb 20, 2017 at 12:23 PM, Ian Lance Taylor <i...@golang.org> wrote: > On Mon, Feb 20, 2017 at 12:06 PM, Will Newton <will.new...@gmail.com> wrote: >> On Thu, Feb 16, 2017 at 9:01 PM, Chris Broadfoot <c...@golang.org> wrote: >>> Hello gophers, >>> >>> We just released Go 1.8. >>> >>> You can read the announcement blog post here: >>> https://blog.golang.org/go1.8 >>> >>> You can download binary and source distributions from our download page: >>> https://golang.org/dl/ >>> >>> To compile from source using a Git checkout, update to the release with "git >>> checkout go1.8" and build as usual. >>> >>> To find out what has changed, read the release notes: >>> https://golang.org/doc/go1.8 >>> >>> Thanks to everyone who contributed to the release. >> >> After upgrading to Go 1.8 from Go 1.7 our testsuite runtime has gone >> up from ~4 minutes to ~20 minutes. We run it with "go test -race >> -covermode=atomic -coverprofile=coverage.tmp" and it seems like one or >> other of coverage or race detector is implicated. Is anything like >> this expected? > > This could possibly be related to https://golang.org/issue/19133 > and/or https://golang.org/issue/19151. > > Ian > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
