Skip to content
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

Jump to bottom

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

Closed
mvdan opened this issue Apr 13, 2022 · 4 comments
Closed

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

mvdan opened this issue Apr 13, 2022 · 4 comments
Labels
FrozenDueToAge 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

@mvdan
Copy link
Member

mvdan commented Apr 13, 2022

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 mvdan added the NeedsFix The path to resolution is known, but the work has not been done. label Apr 13, 2022
@mvdan mvdan added this to the Go1.19 milestone Apr 13, 2022
@mvdan
Copy link
Member Author

mvdan commented Apr 13, 2022

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

@mvdan
Copy link
Member Author

mvdan commented Apr 13, 2022

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.

@mvdan mvdan removed this from the Go1.19 milestone Apr 13, 2022
@mvdan mvdan added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed NeedsFix The path to resolution is known, but the work has not been done. labels Apr 13, 2022
@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Apr 20, 2022
@gopherbot
Copy link

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
Copy link
Member Author

mvdan commented May 20, 2022

I never ran into this warning again, closing SGTM

@golang golang locked and limited conversation to collaborators May 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge 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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mvdan @bcmills @gopherbot