That would be my expectation too.
The explicit export GO111MODULE=on
has broken rclone’s tests
rclone uses go mod
to manage dependencies so there is a go.mod file, however we use go mod vendor
to vendor all the dependencies so we don’t want GO111MODULE=on
.
The cross compile build fails with GO111MODULE=on
for reasons I’m not 100% sure of…
Looking at the changes I see that the presence of a go.mod
is what caused GO111MODULE=on
.
I think since go modules are still experimental that this probably shouldn’t happen for the moment.