-
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
Segmentation fault in LibraryImportGenerator.Unit.Tests #67031
Comments
Tagging subscribers to this area: @dotnet/interop-contrib Issue DetailsObserved in https://dev.azure.com/dnceng/public/_build/results?buildId=1676597&view=results:
For more details please go to the console logs @dotnet/interop-contrib
|
Looking at the last few they're either
or
They seemed to stop on 4/15 though (the 1st kind was last). @jkotas do you recall either of these getting fixed? I can't find them in some quick searching. Execute: Web | Desktop | Web (Lens) | Desktop (SAW) https://engsrvprod.kusto.windows.net/engineeringdata WorkItems
| where FriendlyName == "LibraryImportGenerator.Unit.Tests"
//| where Queued > ago(1d)
| where Status == "BadExit"
| where ExitCode == 134
| join Jobs on JobId
| project
Queued,
FriendlyName, ExitCode,
ConsoleUri,
PhaseName = tostring(parse_json(Properties)["System.PhaseName"]),
Pipeline = tostring(parse_json(Properties).DefinitionName),
BuildId = tostring(parse_json(Properties).BuildId),
QueueName, Source
| where Pipeline == "runtime" |
There is also a Windows dump (no Unix dumps for some reason). It may be unrelated. This was 4/16 on Windows 10 x64. @AndyAyersMS is this something already fixed?
|
I do not see this dump. Also, the stacktrace does not look like anything else mentioned in this issue so far.
The source generator tests are running orders of magnitude more code than other libraries tests, so they will tend to hit intermittent runtime stress bugs more frequently. The next action for this one should be to figure out why we are not getting dumps. We are not going to make progress of intermittent crashes like this without dumps. |
I don't know -- from the stack this seems to be related to the TC mechanism. Looks like there is a windows dump for this merged PR: #67184 under https://dev.azure.com/dnceng/public/_build/results?buildId=1701571&view=ms.vss-test-web.build-test-results-tab
|
Updated query to see windows failures (
|
There are in fact Linux dumps - query error. Execute: Web | Desktop | Web (Lens) | Desktop (SAW) https://engsrvprod.kusto.windows.net/engineeringdata let wi =
WorkItems
| join kind=leftsemi (Jobs | where Queued > ago (30d) | where Source == "ci/public/dotnet/runtime/refs/heads/main") on $left.JobName == $right.Name
| where ExitCode != 0
| where FriendlyName == "LibraryImportGenerator.Unit.Tests";
Files
| lookup kind=inner wi on $left.WorkItemName == $right.Name
| where FileName == "how-to-debug-dump.md"
| project Timestamp, QueueName, ExitCode, Uri, ConsoleUri Gives URL's to get "how-to-debug-dump.md" for these. |
I have looked at number of these and they are all from JIT stress runs, typically hitting asserts in the JIT, not something that runs in standard CI by default. |
Non JIT stress ones too, but on checked CLR, and only up to 4/9. let wi = |
It seems to me we can put aside the Linux issues and use this to track the Windows issues - @AndyAyersMS query works for those. I probably can't debug further myself. Just trying to figure out next actions on these. |
Seems like this crash is perhaps related to #67144 which was fixed on 4/15 by #67922. Perhaps these tests are also stressing collectable assemblies?
|
This failed on linux-arm64 again in #68436. I have opened a fresh issue that is explicitly about the Segmentation fault on linux-arm64 only. |
Observed in https://dev.azure.com/dnceng/public/_build/results?buildId=1676597&view=results:
For more details please go to the console logs
@dotnet/interop-contrib
The text was updated successfully, but these errors were encountered: