This is a weird one...somehow, switching to running Go commands in a container (#14), combined with the passage of time (worked fine for me last week, consistently doesn't this week) has broken the make generate-all task (and the underlying make -f Makefile.metalv1 generate task). But only when I'm running locally.
In CI, make generate-all runs just fine (as it used to do for me locally). Today, locally, it fails every time. After digging through loads of console output I found this message about halfway through:
docker run --rm -u 502:20 -v /Users/ctreatman/Documents/code/equinix-sdk-go:/workdir -w /workdir -e GOCACHE=/tmp/.cache golang:1.19 go mod tidy
go: warning: "all" matched no packages
As a result of this failed execution, the go.mod and go.sum don't declare any dependencies, which eventually causes the Go tests to fail.
This is a weird one...somehow, switching to running Go commands in a container (#14), combined with the passage of time (worked fine for me last week, consistently doesn't this week) has broken the
make generate-all
task (and the underlyingmake -f Makefile.metalv1 generate
task). But only when I'm running locally.In CI,
make generate-all
runs just fine (as it used to do for me locally). Today, locally, it fails every time. After digging through loads of console output I found this message about halfway through:As a result of this failed execution, the
go.mod
andgo.sum
don't declare any dependencies, which eventually causes the Go tests to fail.