Set up an analyzer exception filter to make intermittent failures more actionable. #64836
Conversation
…e actionable. Update the Roslyn Testing SDK version and update the DllImportGenerator unit tests to crash in a way that produces a dump for some of our intermittent issues (dotnet#60909, dotnet#62223). This mechanism will crash the process during the "exception filter" phase, so it will still have the throwing frame on the stack (no unwinding). Hopefully this will enable us to get more actionable dumps to investigate these issues and determine if they're Roslyn bugs or GC holes.
|
Tagging subscribers to this area: @dotnet/interop-contrib Issue DetailsUpdate the Roslyn Testing SDK version and update the DllImportGenerator unit tests to crash in a way that produces a dump for some of our intermittent issues (#60909, #62223). This mechanism will crash the process during the "exception filter" phase, so it will still have the throwing frame on the stack (no unwinding). Hopefully this will enable us to get more actionable dumps to investigate these issues and determine if they're Roslyn bugs or GC holes. cc: @dotnet/interop-contrib
|
|
Mac timeouts are unrelated. Merging in. |
| analyzerExceptionFilter: ex => | ||
| { | ||
| // We're hunting down a intermittent issue that causes NullReferenceExceptions deep in Roslyn. To ensure that we get an actionable dump, we're going to FailFast here to force a process dump. | ||
| if (ex is NullReferenceException) |
There was a problem hiding this comment.
I'd consider always crashing, except for maybe OperationCancelledException, if you produce that. Maybe you'll find some interesting crashes
ghost
locked as resolved and limited conversation to collaborators
3 participants
Update the Roslyn Testing SDK version and update the DllImportGenerator unit tests to crash in a way that produces a dump for some of our intermittent issues (#60909, #62223). This mechanism will crash the process during the "exception filter" phase, so it will still have the throwing frame on the stack (no unwinding). Hopefully this will enable us to get more actionable dumps to investigate these issues and determine if they're Roslyn bugs or GC holes.
cc: @dotnet/interop-contrib
cc: @agocke