-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
rustc.exe -vV
didn't exit successfully (exit code: 0xc000007b) on i686-pc-windows-gnu
#136795
Comments
Out of this range https://github.com/rust-lang/rust/pulls?page=1&q=is%3Apr+merged%3A2025-02-07..2025-02-09+is%3Aclosed+-label%3Arollup, #136588 seems like a possible candidate |
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Reproduces just running @rustbot label -S-needs-repro |
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Do install msys2 in CI explicitly Reverts rust-lang#136588. Only papers over rust-lang#136795, but the root cause needs to be investigated (likely a bug in how `i686-pc-windows-gnu` is built?). Seems like for whatever reason the msys2 installation here is needed for the 32-bit `i686-pc-windows-gnu` target, otherwise `rustc` distributed for that target seems to link against the 64-bit `libwinpthread-1.dll` and such. This revert is mostly just to buy time to investigate without having to debug why the build logic for the 32-bit windows-gnu target is wrong. This reverts commit e060723, reversing changes made to a9e7b30. r? infra cc `@ChrisDenton` `@mati865` try-job: dist-x86_64-msvc try-job: dist-i686-msvc try-job: dist-aarch64-msvc try-job: dist-i686-mingw try-job: dist-x86_64-mingw try-job: dist-x86_64-msvc-alt
From my testing it looks to me like something is forcing |
Prevent Git4Win from prepending its bin directory to `PATH` We used to do this along time ago but we stopped doing it when we started installing msys2 manually. https://github.com/rust-lang/rust/blob/4fd3cf96a1db7771ef4f332b9eb1ad17fa0fd091/src/ci/scripts/install-msys2.sh#L11-L13 Fixes rust-lang#136795 try-job: dist-i686-mingw
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-high |
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
CI: Stop /msys64/bin from being prepended to PATH in msys2 shell We used to do this along time ago but we stopped doing it when we started installing msys2 manually. https://github.com/rust-lang/rust/blob/4fd3cf96a1db7771ef4f332b9eb1ad17fa0fd091/src/ci/scripts/install-msys2.sh#L11-L13 Fixes rust-lang#136795 try-job: dist-i686-mingw
Pin i686-pc-windows-gnu to nightly-2025-02-07 until [1] is resolved. [1]: rust-lang/rust#136795
Rollup merge of rust-lang#136815 - ChrisDenton:fix-mingw-ci, r=Kobzol CI: Stop /msys64/bin from being prepended to PATH in msys2 shell We used to do this along time ago but we stopped doing it when we started installing msys2 manually. https://github.com/rust-lang/rust/blob/4fd3cf96a1db7771ef4f332b9eb1ad17fa0fd091/src/ci/scripts/install-msys2.sh#L11-L13 Fixes rust-lang#136795 try-job: dist-i686-mingw
Reopening to track beta backport nomination of #136815 |
I am seeing a new CI failure with the latest nightly
rust version 1.86.0-nightly (43ca9d18e 2025-02-08)
:rust version 1.86.0-nightly (43ca9d18e 2025-02-08)
works correctly.This happened attempting to build the
libm
crate; however, it looks like this is just failing to runrustc.exe -vV
so it doesn't seem crate-specific. I am still investigating, some work at rust-lang/libm#506.The text was updated successfully, but these errors were encountered: