-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent failure of static_file/file_filter_test.go: TestBasicFiles #30
Comments
Does it always happen with the same test? |
Yep, you can see it happened again on a couple of builds last night: I'm unsure if it happens on the same file in the test table, I'll make the test a little more verbose and run it in a loop overnight to see if I can recreate the issue on my local build server. |
Daves-MacBook-Air-2:falcore dgrijalva$ ruby -e "100.times{r = I can't make it happen on my mac :/ -dave On Aug 20, 2012, at 11:45 AM, Graham Anderson wrote:
|
Does this still happen? |
I've noticed an intermittent failure of this test, here's a sample log from the latest failure.
I first saw the failure on the openSUSE Factory and openSUSE Tumbleweed builders. These are our unstable and rolling release platforms respectivly so after triggering a rebuild and not seeing a direct repeat of the failure I dismissed it as an issue with an unstable platform. Subsequently I have seen the issue maybe two or three time on the current stable release builders and now on an external distro build. Seeing the issue on an external distro prompted me to upstream it.
This intermittently appears on both 32 and 64 bit archs, and across at least the following platforms, but this should be considered with the knowledge that as in intermittent failure, the openSUSE platforms are the ones that get automatically triggered to rebuild more often which increases the likelyhood of occurence.
A first take suggests the error can only originate from the RoundTripper use but poking at the implemtation in the std libs:
http://golang.org/src/pkg/net/http/transport.go?s=3821:3892#L116
I see that there's the use of synch primatives, so this may be a subtle failure and possibly a bug in the test rather than falcore. Additionally we run our Go builds with -p 4 to match the allocated cores on the builders, so I'm not sure if that affects things.
The text was updated successfully, but these errors were encountered: