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
�[0mtest/envoye2e/stackdriver_plugin/cmd/main.go:1: : error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping. (typecheck)
// Copyright 2019 Istio Authors
The weird thing is this seems semi-inconsistent. It fails 100% of the time in our CI after updating to go 1.18, but running locally its inconsistent. Sometimes I can run it 100 times in a row with the same issue, while other times it works 10000 times in a row. I cannot explain this - possibly a cache...?
Root cause
The root cause seems to be b1a53ece68d. I think an approach similar to 90066bf can be used and is more compatible. I will send a fix myself if I am able to get the contribution setup for Go working.
The text was updated successfully, but these errors were encountered:
Fixesgolang#51467.
This uses the same flag already used in
`src/cmd/go/internal/modfetch/codehost/git.go`, and avoids using a new
flag that breaks Ubuntu 16 and Centos 7's latest git.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, it is a regression in 1.18rc1 from 1.17
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
go mod tidy
What did you expect to see?
Success
What did you see instead?
The weird thing is this seems semi-inconsistent. It fails 100% of the time in our CI after updating to go 1.18, but running locally its inconsistent. Sometimes I can run it 100 times in a row with the same issue, while other times it works 10000 times in a row. I cannot explain this - possibly a cache...?
Root cause
The root cause seems to be b1a53ece68d. I think an approach similar to 90066bf can be used and is more compatible. I will send a fix myself if I am able to get the contribution setup for Go working.
The text was updated successfully, but these errors were encountered: