Conversation
|
I suspect this will run into issues with some badly written tests, will do a CI run once it starts working again. |
|
@bors try jobs=apple |
This comment has been minimized.
This comment has been minimized.
Update to Xcode 26.2 try-job: *apple*
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for 16cbdc0 failed: CI. Failed job:
|
|
I think we might need to use the Xcode-provided Clang on @bors try jobs=apple |
This comment has been minimized.
This comment has been minimized.
Update to Xcode 26.2 try-job: *apple*
|
💥 Test timed out after |
|
Hmm. I'd expect the first build with this to take longer because it busts basically the entire build cache, but I wouldn't have expected it to take that long. Maybe it's due to the recent CI outage that GitHub Actions had, which might make jobs slower while they're catching up? I'll wait a few more hours to a day, and then retry the build. |
This comment has been minimized.
This comment has been minimized.
This also updates the macOS runners to run on macOS 15 (the macOS 14 runners only have up to Xcode 16.2 available).
|
@bors try jobs=apple |
This comment has been minimized.
This comment has been minimized.
Update to Xcode 26.2 try-job: *apple*
|
The job Click to see the possible cause of the failure (guessed by this bot) |
Update our CI to run with Xcode 26.
This means that:
rustcandlibstd*.dylib) will have their SDK version raised (before macOS 14.5, now 26.2).The last two points can be observed with:
This shouldn't have much of an effect, but things like
dyldis known to inspect the SDK version, so it might expose some latent bugs (I really don't expect it to though).This also updates the macOS runners to run on macOS 15 (the macOS 14 runners only have up to Xcode 16.2 available). That is desirable anyhow, as the macOS 14 runners will be deprecated in July. This is probably also required for #147192.
r? shepmaster