-
Notifications
You must be signed in to change notification settings - Fork 364
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
Target Debian 12 for testing #5197
base: main
Are you sure you want to change the base?
Conversation
FYI, Debian isn't test on in the CI jobs only in the daily full builds. |
Yeah, I've temporarily enabled it to run here. |
@mikem8361 - I made a custom image to add a missing |
It looks like the tests can't find lldb. It is installed in a non-standard place or with a version in the name we don't look for (i.e. lldb-18). |
If you're looking at the results in the Tests tab, that's from the first run. I did a rerun after fixing the image to include lldb and ran into the timeout. So I think the lldb issue is fixed as there are passing tests showing up in the log output. But it never completes the SOS tests. |
Looks like this version of lldb-14 has some python script problem. I've seen this before but don't remember any solutions. The tests use a python script wrapper that runs the command and captures the error if the command fails. I have a old branch with a C++ lldb extension replacement, but never got it to work correctly.
|
Related to the discussion at dotnet/dotnet-buildtools-prereqs-docker#1276. I want to see if using the Debian 12 Helix image works.