Skip to content
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

Closed
MichalStrehovsky opened this issue Apr 15, 2024 · 7 comments
Closed

Sigsegv in dotnet/msbuild when building repo #101049

MichalStrehovsky opened this issue Apr 15, 2024 · 7 comments
Labels
area-Infrastructure-coreclr Known Build Error Use this to report build issues in the .NET Helix tab

Comments

@MichalStrehovsky
Copy link
Member

MichalStrehovsky commented Apr 15, 2024

Hit in #100945 while building the GenerateHWIntrinsicTests_Arm.csproj project:

2024-04-15T09:34:59.7728930Z     /Users/runner/work/1/s/dotnet.sh: line 27: 91742 Segmentation fault: 11  ${dotnetPath} "$@"
2024-04-15T09:34:59.8872770Z /Users/runner/work/1/s/src/tests/JIT/HardwareIntrinsics/Arm/Directory.Build.targets(15,5): error MSB3073: The command ""/Users/runner/work/1/s/dotnet.sh" build /Users/runner/work/1/s//src/tests/Common/GenerateHWIntrinsicTests/GenerateHWIntrinsicTests_Arm.csproj -c Release --no-restore /p:IntermediateOutputPath=/Users/runner/work/1/s/artifacts/tests/coreclr/obj/osx.x64.Release/Managed/JIT/HardwareIntrinsics/Arm/Sve/Sve_r//GenerateHWIntrinsicTests/ /p:OutputPath=/Users/runner/work/1/s/artifacts/tests/coreclr/osx.x64.Release/JIT/HardwareIntrinsics/Arm/Sve/Sve_r//GenerateHWIntrinsicTests/" exited with code 139. [/Users/runner/work/1/s/src/tests/JIT/HardwareIntrinsics/Arm/Sve/Sve_r.csproj] [/Users/runner/work/1/s/src/tests/build.proj]

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

{
  "ErrorMessage": "Segmentation fault: 11  ${dotnetPath}",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

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

Build Definition Step Name Console log Pull Request
784691 dotnet/runtime Build Tests Log #106599

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 1
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 15, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 15, 2024
@am11
Copy link
Member

am11 commented Apr 15, 2024

It's osx-x64 which seem to have hit it earlier with mono: #67405.

@MichalStrehovsky
Copy link
Member Author

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.

@akoeplinger
Copy link
Member

akoeplinger commented Apr 15, 2024

Also reported in #69588 in 7.0 timeframe, but seems to be super rare. Looks like all of the hits were on macOS.

@akoeplinger akoeplinger changed the title Sigsegv in dotnet when building repo with .NET 9 Preview 3 SDK Sigsegv in dotnet/msbuild when building repo Apr 15, 2024
@akoeplinger akoeplinger added the Known Build Error Use this to report build issues in the .NET Helix tab label Apr 15, 2024
@jkotas jkotas added area-Infrastructure-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 15, 2024
@jkotas
Copy link
Member

jkotas commented Apr 15, 2024

We need to be able to collect crash dumps for builds to make this crash diagnosable.

@MichalStrehovsky
Copy link
Member Author

Also reported in #69588 in 7.0 timeframe, but seems to be super rare. Looks like all of the hits were on macOS.

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.

@am11
Copy link
Member

am11 commented May 27, 2024

1 occurrence in a month, so it was an unlucky run. 😄
Now we are on preview.4.

@agocke
Copy link
Member

agocke commented Sep 11, 2024

Closing as resolved.

@agocke agocke closed this as completed Sep 11, 2024
@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure-coreclr Known Build Error Use this to report build issues in the .NET Helix tab
Projects
Status: Done
Development

No branches or pull requests

5 participants