You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configure CC to refer to a C compiler (or wrapper) that doesn't produce a recognizable version string when run as $CC -### -x c -c -, but works otherwise.
Run go test cmd/go -run=TestScript/cgo_stale_precompiled.
What did you expect to see?
Either the entire test passes (because some other property of the compiler is used as its cache ID instead), or builds that depend on the output artifacts of the C compiler fail with an informative error message.
What did you see instead?
Per #64423, go build commands succeed but the cache fails to distinguish between “no usable C compiler” and “the C compiler is unchanged”: removing the compiler from $PATH erroneously fails to invalidate the cache.
(I am fixing #64423 by fixing the version-parsing logic, but the error-handling bug remains.)
The text was updated successfully, but these errors were encountered:
Go version
go version devel go1.22-098f059d Mon Dec 4 23:03:04 2023 +0000 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
(Forked from #64423.)
CC
to refer to a C compiler (or wrapper) that doesn't produce a recognizable version string when run as$CC -### -x c -c -
, but works otherwise.go test cmd/go -run=TestScript/cgo_stale_precompiled
.What did you expect to see?
Either the entire test passes (because some other property of the compiler is used as its cache ID instead), or builds that depend on the output artifacts of the C compiler fail with an informative error message.
What did you see instead?
Per #64423,
go build
commands succeed but the cache fails to distinguish between “no usable C compiler” and “the C compiler is unchanged”: removing the compiler from$PATH
erroneously fails to invalidate the cache.(I am fixing #64423 by fixing the version-parsing logic, but the error-handling bug remains.)
The text was updated successfully, but these errors were encountered: