test: investigate SQL Server test host SIGSEGV on .NET 10
Description
The Linux .NET 10 SQL Server provider CI job crashed in the native test host immediately after relational database initialization. This appears unrelated to the dissemination changes in #10236: dissemination is opt-in, the crash occurred before any test result, and the corresponding .NET 8 SQL Server job passed.
Evidence
- Run: https://github.com/dotnet/orleans/actions/runs/33940604924
- Failed job: https://github.com/dotnet/orleans/actions/runs/33940604924/job/101237156021
- Commit: f823aad972c206fb944d2997bea92b6aec02497a
- Module:
Orleans.AdoNet.Tests.dll,net10.0, Linux x64 - SQL Server container remained healthy, with no OOM kill or restart.
Initializing relational databases done.
[createdump] Gathering state for process 8947 Orleans.AdoNet.
[createdump] Crashing thread 2301 signal 11 (000b)
[createdump] Writing full dump to file .../Orleans.AdoNet.Tests_8947_crash.dmp
[createdump] Written 632582144 bytes (154439 pages) to core file
Zero tests ran (9s 513ms)
Exit code: 7
Test run summary: Minimum expected tests policy violation, tests ran 0, minimum expected 1The run lists Orleans.AdoNet.Tests_8947_crash.dmp and Orleans.AdoNet.Tests_cc34f843_crash.sequence.log among its diagnostic artifacts. Preserve these artifacts for native crash analysis while available.
Expected behavior
The SQL Server provider suite completes and reports test results.
Investigation
Determine whether the native failure originates in the runtime, coverage instrumentation, or another native dependency. #10888 tracks a similar Linux .NET 10 SIGSEGV in Orleans.Core.Tests; a shared cause has not been established. Searches found no existing report specific to this ADO.NET/SQL Server crash. Recently merged #11102 improves diagnostic retention rather than fixing the crash itself.
Source: dotnet/orleans