-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Disable debuginfo tests for a given blacklist of LLDB versions #34499
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
3f3ef4b
to
cd7681a
Compare
A question, are you sure that it can't be fixed by building against lldb 380 headers? That's what I did for my lldb plugin. |
Thanks @michaelwoerister! I wonder if this logic could perhaps be moved to compiletest to ensure that this is fixed in rustbuild as well? |
@indutny I don't think there's a way to fix these problems the way you suggest (we are not building an LLDB plugin, just using LLDB via Python). |
@alexcrichton Sure, I'll look into it. |
37270f3
to
0e94481
Compare
0e94481
to
f41de0f
Compare
@alexcrichton I've moved the check to compiletest. The version comparison is less fine-grained there but I think that's OK. |
…alexcrichton Disable debuginfo tests for a given blacklist of LLDB versions Anyone having trouble with most LLDB tests failing on OSX, please report your LLDB version here so I can add it to the blacklist. Blacklisted versions so far: * lldb-350.* cc @rust-lang/tools cc @tedhorst @indutny @jonathandturner (people from the original bug report) Fixes rust-lang#32520.
Anyone having trouble with most LLDB tests failing on OSX, please report your LLDB version here so I can add it to the blacklist.
Blacklisted versions so far:
cc @rust-lang/tools
cc @tedhorst @indutny @jonathandturner (people from the original bug report)
Fixes #32520.