-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Net.Requests.Tests, System.Net.Security.Tests failing with Segmentation fault
on Debian 10
#87268
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsBuild InformationBuild error legs:
Tests failing:
Pull request: #86652 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "Segmentation fault",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
|
I'll check whether it could be #87115 |
Updated the search term to use |
System.Net.Quic.Functional.Tests is known issue #87275. System.Net.Requests.Tests is crashing is crashing in libcrypto.so.1.1 initialization on Debian 10. I do not think it has anything to do with the size/speed opt configs, we just happened to hit this problem in these configs first. Unfortunately, it is not possible to get accurate stacktrace to debug this further since Debian does not publish symbols for security updates (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894081). We do not support Debian 10 for .NET 8 according to https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md#linux . We should "fix this" by deleting Debian 10 test runs for .NET 8.
|
Segmentation fault
with Size/Speed optimization configSegmentation fault
on Debian 10
Debian 10 is not supported for .NET 8. Fixes dotnet#87268
Debian 10 is not supported for .NET 8. Fixes #87268
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=298055
Build error legs:
Tests failing:
Pull request: #86652
Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: