cmd/go: provide a way to test that benchmarks work without invalidating cache results #44499
As an experiment I tried doing this for my own day-to-day work, and it was awful. It turns out that the
Invalidating the test cache is probably the right behavior when
This issue tracks the need for “testing that benchmarks still work” without also invalidating cache results.
The text was updated successfully, but these errors were encountered: