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
When building a go binary using remote cache, I get linking errors due to files not found / permissions denied for absolute paths from the remote cache filesystem. This smells like some violation of bazel hermetic rules.
The following archive files contain strings with absolute paths from the remote cache:
Note a workaround is to disable remote cache for GoStdLib build --modify_execution_info=GoStdlib.*=+no-remote in bazelrc as suggested in #2188
What version of rules_go are you using?
v0.39.1
What version of gazelle are you using?
v0.30.0
What version of Bazel are you using?
5.4.1
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
x86 linux
Any other potentially useful information about your toolchain?
Using a gcc version backed in bazel (not system gcc)
What did you do?
Build a go binary using a remote cache
What did you expect to see?
Build passes
What did you see instead?
Linking errors with standard library archive (.a) files which reference absolute paths on the remote cache filesystem which are not present on the local system.
Summary
Possibly related to #1910 or #2188
When building a go binary using remote cache, I get linking errors due to files not found / permissions denied for absolute paths from the remote cache filesystem. This smells like some violation of bazel hermetic rules.
The following archive files contain strings with absolute paths from the remote cache:
Perhaps related to the special case of GoStdLib using absolute paths?
rules_go/go/tools/builders/env.go
Line 37 in a0fb771
Note a workaround is to disable remote cache for GoStdLib
build --modify_execution_info=GoStdlib.*=+no-remote
in bazelrc as suggested in #2188What version of rules_go are you using?
v0.39.1
What version of gazelle are you using?
v0.30.0
What version of Bazel are you using?
5.4.1
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
x86 linux
Any other potentially useful information about your toolchain?
Using a gcc version backed in bazel (not system gcc)
What did you do?
Build a go binary using a remote cache
What did you expect to see?
Build passes
What did you see instead?
Linking errors with standard library archive (
.a)
files which reference absolute paths on the remote cache filesystem which are not present on the local system.Looking in my bazel cache, I do indeed find files which reference absolute paths in the remote cache:
The text was updated successfully, but these errors were encountered: