System.Numerics.Tensors.Tests cause long-running/hanging tests on Mono JIT (not interpreter)

[akoeplinger]

After #97192 was merged we started seeing timeouts in System.Numerics.Tensors.Tests on Mono across all platforms, but seemingly only when using the JIT. Interpreter runs pass fine.

There are a large number of long-running tests like this, but disabling them one-by-one wasn't helpful since then just another test was hanging so I had to disable the whole test project

[Long Running Test] 'System.Numerics.Tensors.Tests.NFloatGenericTensorPrimitives.IndexOfMinMagnitude_ReturnsNegative1OnEmpty', Elapsed: 00:03:17
[Long Running Test] 'System.Numerics.Tensors.Tests.HalfGenericTensorPrimitives.IndexOfMax_ReturnsNegative1OnEmpty', Elapsed: 00:02:03

[nealef]

@uweigand fya

[uweigand]

@giritrivedi @saitama951 can you see if you can recreate this on s390x

[giritrivedi]

Sure @uweigand

[pavelsavara]

I believe this test on NodeJS/WASM is interpreter.
It's very very slow in linear way.
Killed after 1h 15min

Log
Build

[03:57:19] info: [STRT] System.Numerics.Tensors.Tests.NFloatGenericTensorPrimitives.SpanScalarDestination_InPlace(tensorPrimitivesMethod: SpanScalarDestinationDelegate`3 { Method = Void Min[NFloat](System.ReadOnlySpan`1[System.Runtime.InteropServices.NFloat], System.Runtime.InteropServices.NFloat, System.Span`1[System.Runtime.InteropServices.NFloat]), Target = null }, expectedMethod: Func`3 { Method = System.Runtime.InteropServices.NFloat Min(System.Runtime.InteropServices.NFloat, System.Runtime.InteropServices.NFloat), Target = null })
[03:57:19] info: Process 2804 didn't exit within 01:15:00 and will be killed

[03:57:19] info: Killing process tree of 2804...