zeroshade commented on PR #37933: URL: https://github.com/apache/arrow/pull/37933#issuecomment-1749617626
@pitrou @kou Starting with go-1.18, go will attempt to stamp version control information in any binary that is built with the go toolchain. I'm guessing that the config setting up the env isn't maintaining the `.git` folder after the clone or something so it's unable to find the vcs info that it wants to try to stamp the binary. If there's a reason why we're not maintaining the vcs info in the file system for the verification, then it probably makes the most sense to just add the `-buildvcs=false` argument to the build command for the integration test binaries. we're not distributing the binaries built with the verification scripts anyways, so I don't see any problem with disabling the vcs stamping -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
