-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go_sdk.host() leads to unstable unreproducible builds #713
Labels
bug
Something isn't working
build
Build, CI, etc. (w.o. #testing)
contributors
Affects Contributors (not users)
go
Go.dev #golang
help wanted
Extra attention is needed
Comments
vorburger
added
bug
Something isn't working
help wanted
Extra attention is needed
build
Build, CI, etc. (w.o. #testing)
go
Go.dev #golang
contributors
Affects Contributors (not users)
labels
Jun 21, 2024
vorburger
added a commit
to vorburger/enola
that referenced
this issue
Jun 21, 2024
vorburger
added a commit
to vorburger/enola
that referenced
this issue
Jun 21, 2024
vorburger
added a commit
to vorburger/rules_go
that referenced
this issue
Jun 21, 2024
vorburger
added a commit
that referenced
this issue
Jun 21, 2024
vorburger
added a commit
to vorburger/rules_go
that referenced
this issue
Jun 21, 2024
#715 fixed this problem locally for this project. bazel-contrib/rules_go#3967 raised for an "upstream" discussion about this problem (with bazel-contrib/rules_go#3968). |
fmeum
pushed a commit
to bazel-contrib/rules_go
that referenced
this issue
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
build
Build, CI, etc. (w.o. #testing)
contributors
Affects Contributors (not users)
go
Go.dev #golang
help wanted
Extra attention is needed
Expected Behavior
Builds just always just work.
Actual Behavior
Builds regularly break unexpectedly, whenever the version of Go on the host changes; see #626.
Required solution
Replace the
go_sdk.host()
here with a "fixed version of a remote go toolchain".The text was updated successfully, but these errors were encountered: