/ go Public
cmd/go: provide a way to test that benchmarks work without invalidating cache results #44499
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
In #41824 (comment), @rsc wrote:
As an experiment I tried doing this for my own day-to-day work, and it was awful. It turns out that the
-benchtime=1xcauses test results not to be cached, which means that
GOFLAGS=-benchtime=1xcauses every test to be re-run whenever
go testis invoked, even if the source files haven't changed and even if the tests contain no actual benchmarks.
Invalidating the test cache is probably the right behavior when
-benchtimeis actually being used for benchmarking but is entirely inappropriate when the reason for setting the
-benchtimeflag is to test that the benchmarks continue to run successfully (which was the point of #41824 to begin with).
This issue tracks the need for “testing that benchmarks still work” without also invalidating cache results.
CC @jayconrod @matloob
The text was updated successfully, but these errors were encountered: