Add an aarch64-msvc build running on ARM64 Windows#140136
Add an aarch64-msvc build running on ARM64 Windows#140136bors merged 1 commit intorust-lang:masterfrom
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.
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*`
Kobzol
left a comment
There was a problem hiding this comment.
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.
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.
|
(Waiting until at least tomorrow to avoid merging this just before a beta branch). |
|
@bors r+ |
Add an aarch64-msvc build running on ARM64 Windows Resurrecting rust-lang#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*`
|
After a week of debugging, I've narrowed this down to an issue in LLVM: llvm/llvm-project#146973 |
PR to fix the issue in LLVM: llvm/llvm-project#147421 |
|
@bors r+ |
Resurrecting #126341
Per rust-lang/rfcs#3817 we intend to promote
aarch64-pc-windows-msvcto 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-msvcjob will also be run on Arm64 Windows runners.r? @Kobzol
try-job:
*aarch64-msvc*