New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regressions in System.Threading.Tests.Perf_Timer #79409
Comments
ToString regressions are by design. |
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. |
Commit range for System.Threading.Tests.Perf_Timer regression is 41f57b7...9d7ffb5. Because it is threading related, my guess is it is caused by #79091. There is also technically a DateTime change that could be related #79107. |
Tagging subscribers to this area: @dotnet/area-system-threading-tasks Issue DetailsRun Information
Regressions in System.Threading.Tests.Perf_Timer
Reprogit clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Threading.Tests.Perf_Timer*' PayloadsHistogramSystem.Threading.Tests.Perf_Timer.ScheduleManyThenDisposeMany
Description of detection logic
DocsProfiling workflow for dotnet/runtime repository
Regressions in System.Tests.Perf_UInt32
Reprogit clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Tests.Perf_UInt32*' PayloadsHistogramSystem.Tests.Perf_UInt32.ToString(value: 0)
Description of detection logic
DocsProfiling workflow for dotnet/runtime repository Run Information
Regressions in System.Tests.Perf_UInt64
Reprogit clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Tests.Perf_UInt64*' PayloadsHistogramSystem.Tests.Perf_UInt64.ToString(value: 0)
Description of detection logic
DocsProfiling workflow for dotnet/runtime repository
|
I don't think either of those PRs touch code that would be used by that test. |
Fair enough. Could it be another "by design" regression from #79061? None of the other commits seem noteworthy to me. |
I don't think that could be involved either. |
Run Information
Regressions in System.Threading.Tests.Perf_Timer
Test Report
Repro
Payloads
Baseline
Compare
Histogram
System.Threading.Tests.Perf_Timer.ScheduleManyThenDisposeMany
Description of detection logic
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
Regressions in System.Tests.Perf_UInt32
Test Report
Repro
Payloads
Baseline
Compare
Histogram
System.Tests.Perf_UInt32.ToString(value: 0)
Description of detection logic
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
Run Information
Regressions in System.Tests.Perf_UInt64
Test Report
Repro
Payloads
Baseline
Compare
Histogram
System.Tests.Perf_UInt64.ToString(value: 0)
Description of detection logic
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: