-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
build id varies from parallelism #42159
Comments
Does passing |
I assume upgrading to 1.15.3 would also fix the problem, as I can only find closed issues about this problem. |
yes and yes. Would backporting the fixes to 1.14.x be an option? |
I doubt it. From the Minor Releases policy:
This doesn't qualify because it has a very simple workaround. |
Since this is known, fixed at latest, and unlikely to be backported, I'm closing here. |
Fine with me. Soon 1.14 will be obsolete and forgotten. |
While working on reproducible builds for openSUSE, I found that
various binaries in our packages varied in the
.note.go.buildid
ELF section when comparing with a 1-core-VM build.What version of Go are you using (
go version
)?occurred since 1.10
Does this issue reproduce with the latest release?
No. It does not occur with 1.15.3
maybe related to
c5f6920
a3e965c
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
on openSUSE or Debian do
What did you expect to see?
reproducible build results
What did you see instead?
The text was updated successfully, but these errors were encountered: