Test Failure: System.Linq.Tests crashed with SIGSEGV

[JulieLeeMSFT]

Failed in (1):

• runtime-nativeaot-outerloop 20260501.1

Console Log: Console Log
Source: runtime-nativeaot-outerloop / net11.0-linux-Release-x64-NativeAOT_Checked_SpeedOpt_Release-(Debian.13.Amd64.Open)AzureLinux.3.Amd64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-13-helix-amd64@sha256:05e16d140c118f0b1764276949d413dc0a6b9e553c93ef744d18cc950fe41931 / System.Linq.Tests

Failed tests:

- net11.0-linux-Release-x64-NativeAOT_Checked_SpeedOpt_Release-(Debian.13.Amd64.Open)AzureLinux.3.Amd64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-13-helix-amd64@sha256:05e16d140c118f0b1764276949d413dc0a6b9e553c93ef744d18cc950fe41931
  - System.Linq.Tests

Error Message:

./RunTests.sh: line 173:    18 Segmentation fault      (core dumped) ./System.Linq.Tests -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing -xml testResults.xml $RSP_FILE
exit code 139 means SIGSEGV Illegal memory access. Deref invalid pointer, overrunning buffer, stack overflow etc. Core dumped.

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib
See info in area-owners.md if you want to be subscribed.

[MichalStrehovsky]

This was fixed in #127640