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
I've been able to reproduce this a few times myself by running go test -short std in a loop on the linux-amd64-nocgo builder. In case it's relevant, here's the full GOTRACEBACK=crash trace from a timeout:
$ findflakes -grep TestServerValidatesHostHeader
First observed d6a203e 21 Dec 20:21 2015 (184 commits ago)
Last observed 352e287 12 Jan 02:00 2016 (13 commits ago)
28% chance failure is still happening
9.4% failure probability (17 of 172 commits)
Likely culprits:
9% d6a203e cmd/compile: const name and label name may match
8% 97f854c net: make use of IPv4 for parsing routing information on windows
8% 2cf5f04 net: adjust TestInterfaceHardwareAddrWithGetmac
7% 471b6ec api: fix typo in README
6% fbdfa99 runtime: for c-archive/c-shared, don't install unnecessary signal handlers
6% 32cf985 doc: change go1.6 http heading
5% f40c05e runtime: write sigsetstack for Darwin, fix sigaction arg
5% e5ef5d4 doc: add mention of debug.SetTraceback
4% 57337da testing: use debug.SetTraceback("all") to show all goroutines at test timeout
4% bb0567b runtime/debug: add SetTraceback
No known past failures
TestServerValidatesHostHeader is occasionally timing out on the
<-conn.closec
. Here's a recent example from the builders: 2016-01-12T02:00:48-352e287/linux-amd64-race.I've been able to reproduce this a few times myself by running
go test -short std
in a loop on the linux-amd64-nocgo builder. In case it's relevant, here's the full GOTRACEBACK=crash trace from a timeout:The text was updated successfully, but these errors were encountered: