-
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
An error occurred trying to start process 'llvm-symbolizer' #91975
Comments
Tagging subscribers to this area: @hoyosjs Issue DetailsLooks like in some cases there is a failure to run llvm-symbolizer after a crash.
|
I hit this in my PR: #93906 |
@hoyosjs - do we know how we can address this problem? |
I was gathering some data for this one. Things are looking like:
|
@carlossanlop that addresses the runtime queues/containers. I don't have the full list where it matters for libs. |
Removed the known build error label because it masks real crashes from PRs. Example: https://github.com/dotnet/runtime/pull/96386/checks?check_run_id=20196770401 Juan will work on installing LLVM symbolizer on all test machines. |
@hoyosjs just double checking that the expectation here is that this component needs to be added to the helix machines and is not already there nor is it expected to come with the test payload. |
Oddly telemetry only reports this missing in macOS and ubuntu for inner loop scenarios. I can't see any other instances where it's missing except for one alpine group of containers (adding them in dotnet/dotnet-buildtools-prereqs-docker#966). Tracking getting in the queues in #91975. |
@hoyosjs - Sharing some fresh hits from my closely related PR where I am forcing a crash in the common native System.IO.Compression.Brotli code to get some XUnitLogChecker results: #97135
Expand
|
Failed in: runtime-coreclr gcstress-extra 20240525.1 Failed tests:
Error message:
Stack trace:
More failures
|
Looks like in some cases there is a failure to run llvm-symbolizer after a crash.
https://dev.azure.com/dnceng-public/public/_build/results?buildId=403691&view=ms.vss-test-web.build-test-results-tab&runId=8742492&resultId=120074&paneView=debug
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=462152
Error message validated:
An error occurred trying to start process 'llvm-symbolizer' with working directory
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 11/7/2023 11:07:49 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: