-
Notifications
You must be signed in to change notification settings - Fork 13k
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
tests/ui/asan-odr-win/asan_odr_windows.rs
fails on native x86_64-pc-windows-msvc
with lld = true
+ use-lld = true
#135013
Comments
Does it work if you enable |
It does not. Without setting the profile = "compiler"
change-id = 999999
[llvm]
#assertions = true
download-ci-llvm = true
[build]
build = "x86_64-pc-windows-msvc"
profiler = true
sanitizers = true
[rust]
lld = true
use-lld = true
download-rustc = false
codegen-backends = ["llvm"]
deny-warnings = true
debug = false
debuginfo-level = 1
debug-logging = true
debug-assertions = true
debug-assertions-std = true |
(Only this one UI test seems to fail, all other ui tests that are not ignored passes) |
Oh wait, it's looking for
but I only have
|
Actually, I think this test just never works or something... e.g. https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/rustc.20asan/near/237867547
But that message was from May 2021, not sure if still true. |
There's something in bootstrap which seems to address this rust/src/bootstrap/src/core/build_steps/test.rs Lines 2090 to 2094 in ac00fe8
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I don't think that |
(I'll probably revisit this in a few days as I'm working on other things, this is not a major blocker since this requires lld + use-lld on msvc, only wanted to note that this is a thing) |
You're right, it's indeed still
|
Hmm, based on
a bit curious indeed. |
On:
x86_64-pc-windows-msvc
The test
tests/ui/asan-odr-win/asan_odr_windows.rs
fails for me locally if I setrust.lld = true
andrust.use-lld = true
due to
Full test failure output:
Full test failure
Full
config.toml
:Full `config.toml`
The text was updated successfully, but these errors were encountered: