Closed performanceautofiler[bot] closed 2 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Introduced in https://github.com/dotnet/runtime/pull/64861. @Wraith2
More regressions in https://github.com/dotnet/perf-autofiling-issues/issues/3669
Tagging subscribers to this area: @dotnet/area-system-runtime See info in area-owners.md if you want to be subscribed.
Author: | performanceautofiler[bot] |
---|---|
Assignees: | - |
Labels: | `area-System.Runtime`, `untriaged`, `refs/heads/main`, `x64`, `Regression`, `RunKind=micro`, `CoreClr`, `Windows 10.0.18362` |
Milestone: | - |
Closing, this looks to be unrelated and is likely just noise. The test is fairly noisy overall and has had spikes like this in the past and following builds were a bit lower.
Run Information
Regressions in System.Tests.Perf_String
Test Report
Repro
Run Information
Regressions in System.Collections.TryGetValueTrue<Int32, Int32>
Test Report
Repro
Run Information
Regressions in System.Numerics.Tests.Perf_VectorOf<Byte>
Test Report
Repro
Run Information
Regressions in System.Tests.Perf_UInt32
Test Report
Repro
Run Information
Regressions in System.Tests.Perf_Char
Test Report
Repro