-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: cache tests with -race flag #61608
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
Labels
FrozenDueToAge
GoCommand
cmd/go
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Comments
People in #23565 are asking for the caching improvements since 2018. |
tarasmadan
added a commit
to tarasmadan/syzkaller
that referenced
this issue
Jul 27, 2023
If some job is not a build bottleneck - let's remove caching. The main focus points then are "build" and "race" then. To cache test results independently let's use 2 different cache prefixes. See https://markphelps.me/posts/speed-up-your-go-builds-with-actions-cache/. The idea is to always generate cash miss using the second precision key. After the miss we download latest uploaded one using "restore-keys". Potential improvements: 1. golang/go#23565 asks to cache -coverprofile results since 2018. 2. golang/go#61608 to cache -race results.
please provide test code that reproduces the issue. |
github-merge-queue bot
pushed a commit
to google/syzkaller
that referenced
this issue
Aug 23, 2023
If some job is not a build bottleneck - let's remove caching. The main focus points then are "build" and "race" then. To cache test results independently let's use 2 different cache prefixes. See https://markphelps.me/posts/speed-up-your-go-builds-with-actions-cache/. The idea is to always generate cash miss using the second precision key. After the miss we download latest uploaded one using "restore-keys". Potential improvements: 1. golang/go#23565 asks to cache -coverprofile results since 2018. 2. golang/go#61608 to cache -race results.
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
GoCommand
cmd/go
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
go test -race ./...
go test -race ./...
What did you expect to see?
I expected test result to be cached.
Race detector is quite expensive and the results caching is a good thing to have.
What did you see instead?
$ go help test
.....
The rule for a match in the cache is that the run involves the same
test binary and the flags on the command line come entirely from a
restricted set of 'cacheable' test flags, defined as -benchtime, -cpu,
-list, -parallel, -run, -short, -timeout, -failfast, and -v.
If a run of go test has any test or non-test flags outside this set,
the result is not cached.
....
The text was updated successfully, but these errors were encountered: