Closed thanm closed 1 year ago
@golang/release
The solution to this is updating our Debian builders more often. A quick fix may be to add the --allow-releaseinfo-change
flag to the apt-get update
command in racebuild.
We should consider updating to bullseye (current stable), which is supported by the Debian Security Team (rather than the LTS team) in #40561
I believe the builders in question have been updated to Debian Bullseye. Is there any additional work that needs to happen to close this issue?
No objections on my part.
Thanks @thanm. Apologies for this taking a bit longer than anticipated.
What version of Go are you using (
go version
)?Tip for Go, x/build
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?linux/amd64
What did you do?
Ran "racebuild" with tip Go and a recent LLVM commit, e.g.
go build . ./racebuild --goroot=/ssd2/ygo --rev=b6374437af39af66896da74a1dc1b8a0ece26bee --gorev=3e97294663d978bf8abb7acec7cc615ef2f1ea75 870 Steel Stock Rd, Clarksville, Tennessee 37040, United States
What did you expect to see?
Successful run.
What did you see instead?
Many of the linux-line systems targeted by racebuild run "apt" commands to download things like git onto the gomote, so as to use git to download the LLVM repo. These apt commands, e.g. things like this seem to be failing. Here is an example from a linux-arm64 gomote:
Not sure exactly what the issue is here, but it is impacting the ability to update race builders for most of the supported architectures (windows is not impacted, but lots of other os/arch combinations are).