Update: I cannot reproduce the time-out issue any longer. Thanks all.
Still curious to know if there is any way to clean the cache, there used to
be GOCACHE=off, but seems that it's not supported now.
On Friday, March 20, 2020 at 2:01:48 PM UTC+8, xiang...@gmail.com wrote:
>
> I always got a tim
I always got a timeout when running all.bash (synced to the latest commit
cbd421f75b0770c3534d1b641e7770bf1878004f),
it's not reproducible with 'go test -run=. crypto/tls', no GOARCH and GOOS
were set previously. Thanks.
*02:58:18* panic: test timed out after 9m0s*02:58:18* *02:58:18* goroutine
On Thu, Mar 19, 2020 at 10:28 PM Xiangdong JI wrote:
>
> I'm trying to run 'go tool dist test' after the binary has been built
> successfully, while always get a cached result,
> running "go clean -i -r -testcache " and "go clean -cache" in prior
> doesn't help, can anyone please help here?
> Th
Hi,
I'm trying to run 'go tool dist test' after the binary has been built
successfully, while always get a cached result,
running "go clean -i -r -testcache " and "go clean -cache" in prior
doesn't help, can anyone please help here?
Thanks.
$ go tool dist test -run=go_test:crypto/
# go tool d