Closed holiman closed 1 year ago
Thanks for letting know, we are looking into that.
Indeed, gvm install
without -B
option is trying to build Golang distro from sources and exising Golang installation is required as a "bootstrap".
Installing from binaries with -B
works as expected:
https://ci.appveyor.com/project/FeodorFitsner/appveyor-check/builds/44694405
However, go version
not working before using gvm
is another issue and it seems it's only reproducible on GCP environment images. Images on primary cloud work OK and there is a default go1.19 is available:
https://ci.appveyor.com/project/FeodorFitsner/appveyor-check/builds/44694382
I'm going to investigate that.
GCP cloud is used as a backup cloud and I see you've been historically running there for some reason. I'd recommend you to try switching to an in-house Hyper-V cloud by removing APPVEYOR_BUILD_WORKER_CLOUD
environment variable from your builds and see how that goes.
Let me know.
Yes, removing APPVEYOR_BUILD_WORKER_CLOUD
fixed it, thanks. From my perspective this issue can be closed.
OK, thanks for the update!
The appveyor updates as per september 2 says that the
Ubuntu
template containsHowever, it seems to me that this is not true, and it indeed broke our (go-ethereum)
Ubuntu
/Go
builds from that day. Example https://ci.appveyor.com/project/ethereum/go-ethereum/builds/44685236/job/txvt6qjiei64ybnq:So
go
does not exist or is not found.I have done some experimentation.
gvm list
: https://ci.appveyor.com/project/ethereum/go-ethereum/build/job/77fr5lora1vh59a8So
gvm
appears to believe that only an ancient go version is installed.The
$PATH
appears to beUsing
stack
: https://ci.appveyor.com/project/ethereum/go-ethereum/builds/44683950/job/2993ay6u1no2o6u8Tried using
gvm install
: https://ci.appveyor.com/project/ethereum/go-ethereum/builds/44683962/job/2494kjjlofj14625:Apparently
gvm install
doesn't work unless a go version is already present.