-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build: bump Xcode versions on darwin builders #66394
Comments
Change https://go.dev/cl/572595 mentions this issue: |
To 15C500b on macOS 13 and 15E204a on macOS 14. Fixes golang/go#66394 Change-Id: I05a48df1049084c69fbae8c19fad745d2980214d Reviewed-on: https://go-review.googlesource.com/c/build/+/572595 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Michael Knyszek <mknyszek@google.com>
At one point during the pre-LUCI era we actually had two flavors of windows builders, one with ancient compilers (GCC 4.X) and one with more recent compilers. We did tip testing with the "new cc" builders (since the tip linker worked with the newer compilers) but sent CLs on release branches to the "old-cc" builders. I wonder if it might be possible to do something like this in the LUCI world, e.g. have a "darwin-xcode-bleeding-edge" builder or equivalent (caveat: not a LUCI expert, so unsure as to whether this is a viable option). |
Change https://go.dev/cl/582815 mentions this issue: |
Re-applying CL 572595, after the revert in CL 573077. Fixes golang/go#66394 Change-Id: I1f7191c023dfefbdcc37b1340269ae2e3d876c8f Reviewed-on: https://go-review.googlesource.com/c/build/+/582815 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Michael Knyszek <mknyszek@google.com> Auto-Submit: Roland Shoemaker <roland@golang.org>
We re-applied the change, and the versions have now been bumped. |
Bump available Xcode versions to 15.3 on macOS 14 and 15.2 on macOS 13 (the last supported Xcode version). This should unblock some testing for #66360.
The text was updated successfully, but these errors were encountered: