cmd/go: how to disable (run test) Cached #24573

imkos · 2018-03-28T06:00:39Z

What version of Go are you using (`go version`)?

1.10 (win10_x64)

go test, The results always appear cached.
I made an HTTP request, the result of the server return was changed, but the test results were old.
However, run test (cached) does not make HTTP requests
Unless, I modified the code in func Test_** (), the result is the latest

func Test_gotest_cached(t *testing.T) {
	req := NewRequest()
	resp, b_resp, e1 := req.Get("http://10.20.60.52:8080/help")
	if e1 != nil {
		t.Error(e1)
		return
	}
	fmt.Println(string(b_resp), resp.Status)
}

server code:

http.HandleFunc("/help", func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte("hello!"))
	})

go test -v -timeout 30s newpay_svc -run ^Test_gotest_cached$

"hello!" => "hello world!" , but the test results were old.

The text was updated successfully, but these errors were encountered:

myitcv · 2018-03-28T06:05:20Z

The Go project does not use its bug tracker for general discussion or asking questions about the language. The Github bug tracker is only used for tracking bugs and proposals going through the Proposal Process.

Please see the Questions wiki page; it has a list of good places for asking questions.

But as a quick pointer, the Go 1.10 release notes discuss how to disable test caching (and indeed when caching kicks in in the first place):

https://golang.org/doc/go1.10#test

imkos · 2018-03-28T06:21:50Z

Thanks for the reply, I found the reason and the solution.

zyfdegh · 2018-06-01T07:55:32Z

On go1.10

GOCACHE=off go test

davecheney · 2018-06-01T09:00:12Z

go test -count=1

…

On 1 Jun 2018, at 17:55, zyfdegh ***@***.***> wrote: On go1.10 GOCACHE=off go test — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

franciscocpg · 2018-10-05T18:17:35Z

Using go1.11 GOCACHE=off breaks go mod.

So I am using go test -count=1.

zignd · 2018-11-22T18:54:40Z

The idiomatic way to bypass test caching is to use -count=1.

https://golang.org/doc/go1.10#test

Is there any documentation on the -count flag? I'd like to understand its purpose.

myitcv · 2018-11-22T19:04:05Z

Is there any documentation on the -count flag? I'd like to understand its purpose.

https://golang.org/cmd/go/#hdr-Testing_flags

or

go help testflag

lengocgiang · 2019-01-11T16:39:49Z

In vscode
"go.testFlags": ["-count=1"]

Paths names starting with '..' are triggering errors when using Go modules in Go >= 1.11 (1). To work around this we move the testdata into an archive which is unzipped as part of the test. (1) See: golang/go#24573

GOCACHE=off is too strong (prevents reusing binaries) and is going to break when updating to Go 1.12.x. Better use the `-count=1` trick to force a re-run of the tests (golang/go#24573 (comment)).

tj · 2019-11-26T13:15:07Z

Can't say -count is very intuitive. I keep hitting scenarios where test caching is not invalidating correctly, but I haven't pinned down any specific pattern yet. go help test vs go help testflag is a bit awkward as well IMO.

pedromss · 2020-01-09T15:52:07Z

Just arrived at this thread. Is a -no-cache something that could be considered for future versions?
Or maybe print ... (cached, run with -count=1)?

Something that wouldn't force people to google "go test no cache"

EnchanterIO · 2020-01-15T11:54:55Z

+1 @pedromss Just landed here after I was intuitively trying go test -no-cache.

Paths names starting with '..' are triggering errors when using Go modules in Go >= 1.11 (1). To work around this we move the testdata into an archive which is unzipped as part of the test. (1) See: golang/go#24573

ghostsquad · 2020-05-13T18:20:26Z

any chance this can be reopened?

ghostsquad · 2020-05-13T19:10:36Z

@EnchanterIO @pedromss @tj @myitcv @lengocgiang @franciscocpg @davecheney @imkos please upvote the above issue

cristaloleg · 2020-05-13T19:35:12Z

@ghostsquad be patient, please. There is no need to mention everyone.

ghostsquad · 2020-05-13T19:40:30Z

my apologies

arvenil · 2020-06-12T14:19:45Z

I think the best would be if we could do something like t.NoCache() to mark specific tests. Otherwise everyone will just disable cache altogether with -count=1. I run into this problem when I simply changed sql fixture file, so I would like that specific test to run without caching but I would like to cache others.

imkos closed this as completed Mar 28, 2018

ALTree changed the title ~~How to disable (run test) Cached.~~ cmd/go: how to disable (run test) Cached Mar 29, 2018

myitcv mentioned this issue Mar 29, 2018

access: may-start-trybots and go-approvers #24596

Closed

sgreene570 mentioned this issue Jun 20, 2019

Disable Go Unit Test Cache in Go 1.12 openshift/machine-config-operator#873

Merged

polym mentioned this issue Jul 16, 2019

2019 周报 polym/issues#1

Open

ghost mentioned this issue May 13, 2020

proposal: cmd/go: add flag go test -no-cache #39056

Closed

azr mentioned this issue Jun 10, 2020

TestParserReadNetworkingConfig could be randomly failing. hashicorp/packer#9382

Open

This comment has been minimized.

Sign in to view

golang locked as resolved and limited conversation to collaborators Jun 22, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cmd/go: how to disable (run test) Cached #24573

cmd/go: how to disable (run test) Cached #24573

imkos commented Mar 28, 2018 •

edited

myitcv commented Mar 28, 2018

imkos commented Mar 28, 2018

zyfdegh commented Jun 1, 2018

davecheney commented Jun 1, 2018 via email

franciscocpg commented Oct 5, 2018

zignd commented Nov 22, 2018 •

edited

myitcv commented Nov 22, 2018

lengocgiang commented Jan 11, 2019

tj commented Nov 26, 2019 •

edited

pedromss commented Jan 9, 2020

EnchanterIO commented Jan 15, 2020

ghostsquad commented May 13, 2020

ghostsquad commented May 13, 2020

cristaloleg commented May 13, 2020

ghostsquad commented May 13, 2020

arvenil commented Jun 12, 2020 •

edited

This comment has been minimized.

cmd/go: how to disable (run test) Cached #24573

cmd/go: how to disable (run test) Cached #24573

Comments

imkos commented Mar 28, 2018 • edited

What version of Go are you using (go version)?

myitcv commented Mar 28, 2018

imkos commented Mar 28, 2018

zyfdegh commented Jun 1, 2018

davecheney commented Jun 1, 2018 via email

franciscocpg commented Oct 5, 2018

zignd commented Nov 22, 2018 • edited

myitcv commented Nov 22, 2018

lengocgiang commented Jan 11, 2019

tj commented Nov 26, 2019 • edited

pedromss commented Jan 9, 2020

EnchanterIO commented Jan 15, 2020

ghostsquad commented May 13, 2020

ghostsquad commented May 13, 2020

cristaloleg commented May 13, 2020

ghostsquad commented May 13, 2020

arvenil commented Jun 12, 2020 • edited

This comment has been minimized.

imkos commented Mar 28, 2018 •

edited

What version of Go are you using (`go version`)?

zignd commented Nov 22, 2018 •

edited

tj commented Nov 26, 2019 •

edited

arvenil commented Jun 12, 2020 •

edited