You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, the nightly update on 2023-12-02 seems to break the continuous integration (CI) on the basm-rs project on Windows x64 builds (nightly-x86_64-pc-windows-msvc). The Linux x86/x64 builds and the wasm32 builds continue to run fine. The recent commits on the repo is Linux-only and not related to Windows; thus the Windows build should not be affected. It seems like the recently merged pull request 113923 may be relevant.
I expected to see this happen: the basm-rs CI build should continue to pass.
Instead, this happened: the basm-rs CI build fails with a linker error related to compiler-builtins.
Meta
I tried to localize the error with cargo-bisect-rustc on Windows 11 x64 with the msvc toolchain as follows:
Hello, the nightly update on 2023-12-02 seems to break the continuous integration (CI) on the basm-rs project on Windows x64 builds (nightly-x86_64-pc-windows-msvc). The Linux x86/x64 builds and the wasm32 builds continue to run fine. The recent commits on the repo is Linux-only and not related to Windows; thus the Windows build should not be affected. It seems like the recently merged pull request 113923 may be relevant.
I expected to see this happen: the basm-rs CI build should continue to pass.
Instead, this happened: the basm-rs CI build fails with a linker error related to compiler-builtins.
Meta
I tried to localize the error with
cargo-bisect-rustc
on Windows 11 x64 with the msvc toolchain as follows:which results in the following analysis report:
searched nightlies: from nightly-2023-12-01 to nightly-2023-12-03
regressed nightly: nightly-2023-12-02
searched commit range: 87e1447...8c2b577
regressed commit: 8c2b577
bisected with cargo-bisect-rustc v0.6.7
Host triple: x86_64-pc-windows-msvc
Reproduce with:
The actual error message is about unresolved external symbols.
Thanks in advance!
The text was updated successfully, but these errors were encountered: