cmd/dist: throws a trailing warning on master due to recent changes

[mvdan]

I just pulled Go master, up to b55a2fb from a previous 2b31abc, and the Go build via cd src && GOGC=off GOAMD64=v3 ./make.bash -v started failing:

[...]
cmd/go/internal/list
cmd/go/internal/vet
cmd/go/internal/modget
cmd/go/internal/test
cmd/go/internal/bug
cmd/go
go tool dist: unexpected stale targets reported by /home/mvdan/tip/pkg/tool/linux_amd64/go_bootstrap list -gcflags="" -ldflags="" for [std cmd] (consider rerunning with GOMAXPROCS=1 GODEBUG=gocachehash=1):
	STALE cmd/trace: not installed but available in build cache

It's unclear what caused this; I'll try to bisect. It seems like some form of regression in the past couple of days.

[mvdan]

I should clarify I'm bootstrapping via go version go1.18 linux/amd64.

[mvdan]

Hmm; I re-ran on the same master commit with a clean checkout, and it no longer fails. Weird. So I'm not able to bisect.

[gopherbot]

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.)

[mvdan]

I never ran into this warning again, closing SGTM