-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Add an aarch64-msvc build running on ARM64 Windows #140136
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
base: master
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #138591) made this pull request unmergeable. Please resolve the merge conflicts. |
b26ede0
to
6677d07
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
d729d12
to
4f5a07f
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[win][ci] Update LLVM toolchain used to build LLVM to 20 While trying to get the aarch64-msvc build working correctly (rust-lang#140136), I needed to update the version of LLVM used to build LLVM in Windows CI runners to 20 (as this has improved support for Arm64 and Arm64EC on Windows). This catches Windows up to Linux which was updated to 20 by rust-lang#137189 try-job: `x86_64-apple-*` try-job: `aarch64-apple` try-job: `x86_64-msvc-*` try-job: `i686-msvc-*` try-job: `x86_64-mingw-*`
All cleanups have now been merged, so I've filed the MCP: rust-lang/compiler-team#875 |
Oh, sorry, I thought that this is a bump to Tier 2 with host tools, not to Tier 1. That indeed requires a full RFC, not just an MCP. |
☔ The latest upstream changes (presumably #141320) made this pull request unmergeable. Please resolve the merge conflicts. |
Filed the RFC: rust-lang/rfcs#3817 |
does this need to update a bunch of submodules? those should probably be separate PRs |
ffce8e0
to
56f27af
Compare
No submodule changes were needed: that was my mistake of rebasing then forgetting to update the submodules. |
@bors2 try |
Add an aarch64-msvc build running on ARM64 Windows Resurrecting #126341 Per <rust-lang/rfcs#3817> we intend to promote `aarch64-pc-windows-msvc` to Tier 1. As part of that work, we are adding a pre-merge CI job to validate that changes do not break this target. Additionally, for consistency, the `dist-aarch64-msvc` job will also be run on Arm64 Windows runners. r? `@Kobzol` try-job: `*aarch64-msvc*`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. If the try build is green, I'll approve it.
|
||
source "$(cd "$(dirname "$0")" && pwd)/../shared.sh" | ||
|
||
if [[ "${CI_JOB_NAME}" = *aarch64* ]] && isWindows; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather do this via an explicit parameter in jobs.yml
(such as e.g. free_disk
), but for now this is fine, as I expect we'll remove this soon-ish.
💔 Test failed
|
Add a missing colon at the end of the panic location details in location-detail-unwrap-multiline.rs The `location-detail-unwrap-multiline` test was failing when trying to enable `aarch64-pc-windows-msvc` CI Runners: rust-lang#140136 (comment) When debugging, the normalized stderr was: ``` thread 'main' panicked at $DIR/location-detail-unwrap-multiline.rs:11:10: called `Option::unwrap()` on a `None` value stack backtrace: note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. ``` Note the trailing colon at the end of the location details in the panic message. This was missing in the error pattern regex. No idea why it has been passing for all other targets and failed for `aarch64-pc-windows-msvc`, but with the trailing colon it is now passing for all.
Rollup merge of #142639 - dpaoliello:needcolon, r=WaffleLapkin Add a missing colon at the end of the panic location details in location-detail-unwrap-multiline.rs The `location-detail-unwrap-multiline` test was failing when trying to enable `aarch64-pc-windows-msvc` CI Runners: #140136 (comment) When debugging, the normalized stderr was: ``` thread 'main' panicked at $DIR/location-detail-unwrap-multiline.rs:11:10: called `Option::unwrap()` on a `None` value stack backtrace: note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. ``` Note the trailing colon at the end of the location details in the panic message. This was missing in the error pattern regex. No idea why it has been passing for all other targets and failed for `aarch64-pc-windows-msvc`, but with the trailing colon it is now passing for all.
@Kobzol test issue has been fixed, this is ready to be merged now. |
@bors2 try |
Add an aarch64-msvc build running on ARM64 Windows Resurrecting #126341 Per <rust-lang/rfcs#3817> we intend to promote `aarch64-pc-windows-msvc` to Tier 1. As part of that work, we are adding a pre-merge CI job to validate that changes do not break this target. Additionally, for consistency, the `dist-aarch64-msvc` job will also be run on Arm64 Windows runners. r? `@Kobzol` try-job: `*aarch64-msvc*`
Add a missing colon at the end of the panic location details in location-detail-unwrap-multiline.rs The `location-detail-unwrap-multiline` test was failing when trying to enable `aarch64-pc-windows-msvc` CI Runners: rust-lang/rust#140136 (comment) When debugging, the normalized stderr was: ``` thread 'main' panicked at $DIR/location-detail-unwrap-multiline.rs:11:10: called `Option::unwrap()` on a `None` value stack backtrace: note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. ``` Note the trailing colon at the end of the location details in the panic message. This was missing in the error pattern regex. No idea why it has been passing for all other targets and failed for `aarch64-pc-windows-msvc`, but with the trailing colon it is now passing for all.
Resurrecting #126341
Per rust-lang/rfcs#3817 we intend to promote
aarch64-pc-windows-msvc
to Tier 1. As part of that work, we are adding a pre-merge CI job to validate that changes do not break this target.Additionally, for consistency, the
dist-aarch64-msvc
job will also be run on Arm64 Windows runners.r? @Kobzol
try-job:
*aarch64-msvc*