[Test Package Versions Bump] Updating package versions#8593
Conversation
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (8593) and master. ✅ No regressions detected - check the details below Full Metrics ComparisonFakeDbCommand
HttpMessageHandler
Comparison explanationExecution-time benchmarks measure the whole time it takes to execute a program, and are intended to measure the one-off costs. Cases where the execution time results for the PR are worse than latest master results are highlighted in **red**. The following thresholds were used for comparing the execution times:
Note that these results are based on a single point-in-time result for each branch. For full results, see the dashboard. Graphs show the p99 interval based on the mean and StdDev of the test run, as well as the mean value of the run (shown as a diamond below the graph). Duration chartsFakeDbCommand (.NET Framework 4.8)gantt
title Execution time (ms) FakeDbCommand (.NET Framework 4.8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (72ms) : 70, 75
master - mean (74ms) : 70, 78
section Bailout
This PR (8593) - mean (76ms) : 75, 78
master - mean (80ms) : 76, 84
section CallTarget+Inlining+NGEN
This PR (8593) - mean (1,129ms) : 1082, 1177
master - mean (1,125ms) : 1079, 1172
FakeDbCommand (.NET Core 3.1)gantt
title Execution time (ms) FakeDbCommand (.NET Core 3.1)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (115ms) : 111, 120
master - mean (117ms) : 110, 124
section Bailout
This PR (8593) - mean (119ms) : 113, 126
master - mean (115ms) : 111, 119
section CallTarget+Inlining+NGEN
This PR (8593) - mean (808ms) : 786, 829
master - mean (812ms) : 786, 837
FakeDbCommand (.NET 6)gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (104ms) : 99, 109
master - mean (101ms) : 96, 106
section Bailout
This PR (8593) - mean (102ms) : 98, 106
master - mean (106ms) : 101, 111
section CallTarget+Inlining+NGEN
This PR (8593) - mean (948ms) : 911, 985
master - mean (945ms) : 903, 988
FakeDbCommand (.NET 8)gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (101ms) : 96, 106
master - mean (101ms) : 97, 104
section Bailout
This PR (8593) - mean (104ms) : 100, 108
master - mean (100ms) : 98, 103
section CallTarget+Inlining+NGEN
This PR (8593) - mean (842ms) : 771, 914
master - mean (836ms) : 772, 899
HttpMessageHandler (.NET Framework 4.8)gantt
title Execution time (ms) HttpMessageHandler (.NET Framework 4.8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (203ms) : 192, 214
master - mean (205ms) : 197, 214
section Bailout
This PR (8593) - mean (206ms) : 196, 216
master - mean (209ms) : 201, 218
section CallTarget+Inlining+NGEN
This PR (8593) - mean (1,262ms) : 1214, 1309
master - mean (1,257ms) : 1213, 1301
HttpMessageHandler (.NET Core 3.1)gantt
title Execution time (ms) HttpMessageHandler (.NET Core 3.1)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (299ms) : 279, 318
master - mean (295ms) : 281, 309
section Bailout
This PR (8593) - mean (298ms) : 284, 312
master - mean (292ms) : 277, 306
section CallTarget+Inlining+NGEN
This PR (8593) - mean (1,004ms) : 979, 1030
master - mean (995ms) : 976, 1014
HttpMessageHandler (.NET 6)gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (290ms) : 276, 305
master - mean (284ms) : 269, 298
section Bailout
This PR (8593) - mean (292ms) : 277, 306
master - mean (284ms) : 270, 297
section CallTarget+Inlining+NGEN
This PR (8593) - mean (1,177ms) : 1124, 1230
master - mean (1,163ms) : 1134, 1192
HttpMessageHandler (.NET 8)gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8593) - mean (289ms) : 272, 306
master - mean (284ms) : 268, 300
section Bailout
This PR (8593) - mean (290ms) : 271, 309
master - mean (284ms) : 268, 301
section CallTarget+Inlining+NGEN
This PR (8593) - mean (1,060ms) : 991, 1130
master - mean (1,055ms) : 979, 1132
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
BenchmarksBenchmark execution time: 2026-05-10 01:52:30 Comparing candidate commit 01d6805 in PR branch Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥 Scenarios present only in baseline:
Found 3 performance improvements and 4 performance regressions! Performance is the same for 45 metrics, 20 unstable metrics, 87 known flaky benchmarks, 39 flaky benchmarks without significant changes.
|
## Summary of changes Exclude `OpenTelemetry.Api` benchmark results from PR comment comparison. ## Reason for change As a follow up to enabling OTel microbenchmarks, the PR comment has become very noisy, as it's expecting all the benchmarks, even though we don't run them on PRs. #8593 (comment) ## Implementation details Filter out `candidate.OpenTelemetry.Api.*` files when globbing for candidate results in `post-pr-comment.sh`. These benchmarks only run on master (Nuke doesn't build `Benchmarks.OpenTelemetry.Api` on PRs), so including them causes "scenarios present only in baseline" warnings. ## Test coverage CI pipeline on this branch. ## Other details <!-- Fixes #{issue} -->
Updates the package versions for integration tests. See below for a summary of the changes.
Package Version Updates
Bold entries indicate major-version bumps.
(new)means no previous version existed.