-
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
[NativeAOT] SIGABRT Crash in System.Security.Cryptography.OpenSsl.Tests #79619
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones Issue DetailsSaw the failure in: The latter is a noop PR with no code changes.
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsSaw the failure in: The latter is a noop PR with no code changes.
|
It seems like an infrastructure issue where some runs are using macOS machines that don't have a proper version of OpenSSL on them. This seems like a recurrence of #73210 at first glance. |
@MattGal since you helped us with the previous issue... is it possible we have another macOS machine in the pool that does not have OpenSSL? |
I'm taking a look and will let you know what I find. Nothing interesting should have changed w/ the test macs recently. |
#79578 also had this failure. |
@VSadov checking it out there's definitely a pattern of this happening on osx.1200.amd64.open & osx.1200.arm64.open, I opened dotnet/arcade#11943 and will try to figure out what broke today. |
@VSadov I'll put notes in the other issue, but the machines in that queue have not been reimaged or changed recently in any way, and the libraries we'd expect there from the previous issue are all there: |
I am not an expert in these tests or what OpenSSL does, I just did a test run and saw the failure and then I saw this failure in other runs. I think the environment expectations would not be different from a regular (not NativeAOT) case. NativeAOT also should use the same native PAL libraries, linked into the executable. |
Nevermind, that's in the screenshot. Reading helps. |
Is it only happening on NativeAOT runs? Are non-nativeAOT runs passing on these machines, or failing, too? |
As I look at #79591 I see only NativeAOT and couple Mono legs having failures and Mono failures seem unrelated (somehting with System.Text.Json.Tests) So I guess CoreCLR counterparts for these tests are passing. They could be running on different machine, but I do not know if that matters. |
I am pretty sure these tests were not really running on NativeAOT until relatively recently. I fixed the OpenSSL native interop linkage somewhere along the macOS bring-up (mostly to get (Maybe I misremembered the timeline; seems like the tests were reenabled by #72294 which landed in August while most of my bringup patches only landed in September; so perhaps I didn't have that commit early on but eventually rebased past it) |
@VSadov I think I found it. Specifically, it was fallout from https://github.com/dotnet/arcade/issues/11631 , "llvm-symbolizer not present in base queue". Addressing that made DDFUN run brew update, which moved them from having OpenSSL 1.1.1k to 1.1.1s without fixing those links. While the links exist, they didn't actually go to the files they should. I've fixed this up on osx.1200.arm64.open and will keep an eye on it until the tests pass again. |
@VSadov I have my ways... I'll keep dotnet/arcade#11943 open until I see it working either way. |
@VSadov I think it's fixed, feel free to reopen the linked arcade issue if(when) it comes back. |
No hits in last 7 days |
Saw the failure in:
#79519 and
#79578
#79591
The #79591 is a noop PR with no code changes.
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-79591-merge-93e036f2375b4c6a89/System.Security.Cryptography.OpenSsl.Tests/1/console.644fc1d2.log?helixlogtype=result
Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: