Dmitri Shuralyov

CC @FiloSottile, @katiehockman, @rolandshoemaker, @kevinburke via [owners](https://dev.golang.org/owners).

For additional context, this [comment thread](https://go-review.git.corp.google.com/c/go/+/448802/4..7/src/cmd/dist/test.go#b359) captures some of the reasons why `-run=^$` was chosen over test -c at the time, before we considered this use case.

There were a lot of internal refactors and clean up work done as part of being able to add proper -json flag support to cmd/dist (#37486), and that lead up...

> unless we're planning to refresh the `x` dependencies one more time before the final release. (@golang/release can confirm whether that is the case?) We create internal vendor branches for...

I tried `go test -v ./ssh/test -run=^TestAgentForward$` on another Mac which is closer to a "default out of the box" setup, running macOS 14.2.1 (23C71), and the issue reproduces on...

I recall @adonovan used a GOPLSCACHE mechanism to help with that in the previous infrastructure ([CL 494297](https://go.dev/cl/494297)). I'm not seeing that in the LUCI infrastructure—perhaps it needs to be ported...

Reports above seem to be because the `GO_TEST_TIMEOUT_SCALE=2` env var wasn't fully propagated to the environment of one of the two builders. That should be fixed for future builds ([CL...

The "darwin-amd64-13" builder on the old dashboard doesn't have `GO_TEST_TIMEOUT_SCALE` in its configuration, so this isn't a case of that not being ported over. Perhaps our macOS amd64 13 builder...

We discussed and looked into this a bit. This turns out not to be a consistent slowness: looking at https://ci.chromium.org/ui/p/golang/builders/ci/gotip-darwin-amd64_13 briefly shows many builds complete successfully in 15-20 min, with...

To clarify, in that entry, the idea was that the comment was implicit and therefore not required. > So, *without needing to write the comment*, the above is implicitly understood...