[CI Visibility] honor EFD retry mode over ATR#8288
Conversation
BenchmarksBenchmark execution time: 2026-03-18 13:57:46 Comparing candidate commit 64b83c9 in PR branch Found 10 performance improvements and 9 performance regressions! Performance is the same for 159 metrics, 14 unstable metrics. scenario:Benchmarks.Trace.AgentWriterBenchmark.WriteAndFlushEnrichedTraces net6.0
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.AllCycleSimpleBody netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecBodyBenchmark.ObjectExtractorSimpleBody netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeArgs netcoreapp3.1
scenario:Benchmarks.Trace.Asm.AppSecEncoderBenchmark.EncodeLegacyArgs netcoreapp3.1
scenario:Benchmarks.Trace.AspNetCoreBenchmark.SendRequest net6.0
scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net472
scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces net6.0
scenario:Benchmarks.Trace.CIVisibilityProtocolWriterBenchmark.WriteAndFlushEnrichedTraces netcoreapp3.1
scenario:Benchmarks.Trace.CharSliceBenchmark.OptimizedCharSlice net6.0
scenario:Benchmarks.Trace.Log4netBenchmark.EnrichedLog netcoreapp3.1
scenario:Benchmarks.Trace.SingleSpanAspNetCoreBenchmark.SingleSpanAspNetCore net6.0
scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope net6.0
scenario:Benchmarks.Trace.SpanBenchmark.StartFinishScope netcoreapp3.1
scenario:Benchmarks.Trace.SpanBenchmark.StartFinishSpan netcoreapp3.1
scenario:Benchmarks.Trace.TraceAnnotationsBenchmark.RunOnMethodBegin net6.0
|
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (8288) 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 (8288) - mean (69ms) : 68, 71
master - mean (71ms) : 70, 73
section Bailout
This PR (8288) - mean (73ms) : 71, 75
master - mean (76ms) : 75, 77
section CallTarget+Inlining+NGEN
This PR (8288) - mean (1,056ms) : 987, 1126
master - mean (1,061ms) : 1023, 1099
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 (8288) - mean (108ms) : 105, 111
master - mean (111ms) : 109, 114
section Bailout
This PR (8288) - mean (109ms) : 107, 111
master - mean (113ms) : 111, 114
section CallTarget+Inlining+NGEN
This PR (8288) - mean (730ms) : 714, 747
master - mean (744ms) : 724, 764
FakeDbCommand (.NET 6)gantt
title Execution time (ms) FakeDbCommand (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8288) - mean (96ms) : 93, 99
master - mean (99ms) : 96, 102
section Bailout
This PR (8288) - mean (97ms) : 95, 99
master - mean (99ms) : 97, 101
section CallTarget+Inlining+NGEN
This PR (8288) - mean (711ms) : 677, 744
master - mean (723ms) : 676, 769
FakeDbCommand (.NET 8)gantt
title Execution time (ms) FakeDbCommand (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8288) - mean (95ms) : 92, 98
master - mean (98ms) : 95, 100
section Bailout
This PR (8288) - mean (96ms) : 95, 98
master - mean (99ms) : 98, 101
section CallTarget+Inlining+NGEN
This PR (8288) - mean (650ms) : 624, 677
master - mean (657ms) : 634, 681
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 (8288) - mean (200ms) : 188, 212
master - mean (194ms) : 189, 200
section Bailout
This PR (8288) - mean (200ms) : 194, 206
master - mean (197ms) : 193, 201
section CallTarget+Inlining+NGEN
This PR (8288) - mean (1,177ms) : 1115, 1238
master - mean (1,162ms) : 1090, 1233
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 (8288) - mean (282ms) : 275, 290
master - mean (277ms) : 273, 282
section Bailout
This PR (8288) - mean (282ms) : 277, 288
master - mean (279ms) : 273, 285
section CallTarget+Inlining+NGEN
This PR (8288) - mean (916ms) : 874, 957
master - mean (904ms) : 873, 936
HttpMessageHandler (.NET 6)gantt
title Execution time (ms) HttpMessageHandler (.NET 6)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8288) - mean (279ms) : 265, 292
master - mean (271ms) : 265, 277
section Bailout
This PR (8288) - mean (276ms) : 269, 283
master - mean (271ms) : 268, 274
section CallTarget+Inlining+NGEN
This PR (8288) - mean (956ms) : 915, 998
master - mean (938ms) : 903, 973
HttpMessageHandler (.NET 8)gantt
title Execution time (ms) HttpMessageHandler (.NET 8)
dateFormat x
axisFormat %Q
todayMarker off
section Baseline
This PR (8288) - mean (274ms) : 268, 280
master - mean (271ms) : 264, 278
section Bailout
This PR (8288) - mean (277ms) : 267, 286
master - mean (271ms) : 265, 276
section CallTarget+Inlining+NGEN
This PR (8288) - mean (858ms) : 825, 892
master - mean (840ms) : 810, 870
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
E2E Test Report: SUCCESS ✅Tested by: Shepherd Agent (autonomous QA for Datadog Test Optimization) Test Environment
ResultsTest 1: Default scenario (baseline regression check)
Test 2: Combined EFD + ATR scenario (PR-specific verification)Scenario:
Key VerificationThe core fix was confirmed: when both EFD and ATR are enabled, retry spans for new tests carry Test Methodology
This E2E test was performed by Shepherd — autonomous QA agent for Datadog Test Optimization |
andrewlock
left a comment
There was a problem hiding this comment.
LGTM as far as I can tell, though I didn't verify the logic extensively. Just a few (non-blocking) nits and suggestions for cleanup/de-dupe, feel free to take/ignore 😄
12c5b58 to
64b83c9
Compare
Summary
Fix the combined EFD + ATR case across .NET test frameworks so retry metadata matches the retry executor that actually ran.
What Changed
all_efd_with_atrscenarios for NUnit, MSTest v2, xUnit v2, and xUnit v3.Framework Notes
Snapshot Check
The new
all_efd_with_atrsnapshots match the intended behavior across frameworks:test.retry_reason: efd, 0 taggedatr.post_2_2_4): 148 total, 126 retry events, all 126 taggedtest.retry_reason: efd, 0 taggedatr.test.retry_reason: efd, 0 taggedatr.test.retry_reason: efd, 0 taggedatr.Concrete examples from the snapshots:
SimplePassTestappears 10 times in every framework snapshot, which confirms EFD execution is active because ATR would not retry a passing test.SimpleErrorParameterizedTestappears 30 times in NUnit/xUnit because 3 parameter sets each get the 10 EFD executions.test.has_failed_all_retries: true.post_2_2_4path, the newall_efd_with_atrsnapshots are byte-for-byte identical to the existingall_efdbaselines, which is the expected outcome.Verification
dotnet test tracer/test/Datadog.Trace.ClrProfiler.IntegrationTests/Datadog.Trace.ClrProfiler.IntegrationTests.csproj -c Release --no-build --framework net6.0 --filter "FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.NUnitEvpTests.EarlyFlakeDetection|FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.TcpXUnitEvpTests.EarlyFlakeDetection"dotnet test tracer/test/Datadog.Trace.ClrProfiler.IntegrationTests/Datadog.Trace.ClrProfiler.IntegrationTests.csproj -c Release --no-build --framework net8.0 --filter "FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.XUnitEvpTestsV3.EarlyFlakeDetection"dotnet test tracer/test/Datadog.Trace.ClrProfiler.IntegrationTests/Datadog.Trace.ClrProfiler.IntegrationTests.csproj -c Release --no-build --framework net9.0 --filter "FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.MsTestV2EvpTests.EarlyFlakeDetection"dotnet test tracer/test/Datadog.Trace.ClrProfiler.IntegrationTests/Datadog.Trace.ClrProfiler.IntegrationTests.csproj -c Release --no-build --framework net9.0 --filter "FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.NUnitRetriesTests.FlakyRetries|FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.XUnitRetriesTests.FlakyRetries|FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.MsTestV2RetriesTests.FlakyRetries|FullyQualifiedName~Datadog.Trace.ClrProfiler.IntegrationTests.CI.XUnitRetriesTestsV3.FlakyRetries"