-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Sigsegv in dotnet/msbuild when building repo #101049
Comments
It's osx-x64 which seem to have hit it earlier with mono: #67405. |
We're crashing when we run dotnet.sh (in both bugs) - I don't think the runtime involved is Mono. This is the dotnet that is used to build the repo and that's CoreCLR-based. I think #67405 was misrouted and should likely be just closed because it's stale. |
Also reported in #69588 in 7.0 timeframe, but seems to be super rare. Looks like all of the hits were on macOS. |
We need to be able to collect crash dumps for builds to make this crash diagnosable. |
My concern was that if we hit this in one of two runs, it might not be super rare in this SDK (or it was just a very unlucky run), but I guess we'll see soon enough and can revert if needed. |
1 occurrence in a month, so it was an unlucky run. 😄 |
Closing as resolved. |
Hit in #100945 while building the GenerateHWIntrinsicTests_Arm.csproj project:
We don't have a dump because the infra is not capable of collecting dumps on the build machine. Hit on a macOS machine, so could be macOS specific, but it's also non-deterministic, so...
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=643372
Build error leg or test failing: Build osx-x64 Release AllSubsets_Mono_Minijit_RuntimeTests minijit
Pull request: #100945
Error Message
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=643372
Error message validated:
[Segmentation fault: 11 ${dotnetPath}
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/15/2024 1:07:45 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: