Tracking missed regressions from auto-filing

[DrewScoggins]

As I work through these investigations I will update this issue, and link to any issues that are opened as a result.

Regressions

By design

• [ ] System.Numerics.Tests.Perf_VectorConvert.Convert_double_long:
  • seems to be missed by the bot
  • opened: https://github.com/dotnet/runtime/issues/65189
  • explained: https://github.com/dotnet/runtime/issues/65189#issuecomment-1036388904

Need to investigate why this was missed.

Investigation in progress

• [ ] System.Collections.IterateForEach<String>.SortedSet
  • it's not visible in the Reporting System, but I can reproduce it locally.
  • opened: https://github.com/dotnet/runtime/issues/65190

This is almost certainly related to either the hardware in the lab, or the difference in executing the test code (SDK vs CoreRun)

• [ ] System.Numerics.Tests.Perf_Matrix4x4.MultiplyByScalarOperatorBenchmark, System.Numerics.Tests.Perf_Matrix4x4.Transpose, > System.Numerics.Tests.Perf_Matrix4x4.NegateBenchmark, System.Numerics.Tests.Perf_Matrix4x4.MultiplyByScalarBenchmark
  • seems to be missed by the bot
  • opened https://github.com/dotnet/runtime/issues/65191

This regression was found, https://github.com/dotnet/runtime/issues/59415, but these particular benchmarks were not also flagged as part of the regression. I will take a look at what happened, and why these were not included.

• [ ] System.Tests.Perf_Version.Parse2
  • seems to be missed by the bot
  • opened: https://github.com/dotnet/runtime/issues/65193
  • Unix specific
  • most likely caused by a PGO data update

These will need to be investigated

[DrewScoggins]

@adamsitnik @danmoseley @AndyAyersMS @kunalspathak