-
Notifications
You must be signed in to change notification settings - Fork 18k
x/build/cmd/release: leave oldlink binary out of RC1 (if the beta doesn't uncover serious linker issues) #39509
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
Comments
/cc @jeremyfaller @thanm I think it's a good idea to include this in the beta. While our internal testing gets good coverage of certain configurations, it doesn't get very good coverage of others, and shipping this in the beta will help with any problems uncovered there. However, the new linker roll out has been going really smoothly so far. Assuming the beta doesn't uncover any serious linker issues, I'd be inclined to leave oldlink out of the RC. |
@aclements 's suggestion SGTM. A test may fail if the old linker is not present. We could change the test to skip if the binary does not exist. |
I'm happy with @aclements 's suggestion too. |
It was really @toothrot 's suggestion, so I think we're all in agreement. :) |
@cherrymui Were you referring to a specific test? Or did you mean we should look for such tests and update them as needed? I can try to find anything by taking go1.15beta1, removing the |
|
Thanks! This is how the test fails when
It's going to affect people who try to run Given that 1.15 is shipping a new linker, it's better to avoid misleading test failures, so skipping the test if |
Change https://golang.org/cl/242604 mentions this issue: |
The binary was removed from releases in https://golang.org/cl/242643, but the commit message incorrectly failed to mention the repository to reference this issue. |
As part of https://golang.org/s/better-linker, we now build a binary called
oldlink
in our release of Go. While it may be useful to include in the beta, we should make a decision on whether this is included in the RC or final releases of Go 1.15, vs asking people to rebuild it on their own if necessary./cc @cherrymui @aclements @golang/osp-team
The text was updated successfully, but these errors were encountered: