Closed andrewlock closed 1 month ago
Branch report: andrew/fix-instrumentation
Commit report: 5f454ef
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 301984 Passed, 1618 Skipped, 12h 31m 1.95s Total Time
Execution-time results for samples comparing the following branches/commits:
Execution-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 shown 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).
Benchmarks for #5949 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Summary of changes
Fix bug in v3 instrumentation of
new TracerSettings(bool useDefaultSources)
Reason for change
We were missing a parameter in the instrumentation
Implementation details
Add the missing parameter
Test coverage
We don't have a good coverage for this and I'm not sure the best way to catch it in the future tbh 🤔 Typically we catch these when developing integrations.
I guess in this case the best way is to call every API and check for the side effects, but that also feels like a lot of work, so inclined to just YOLO it unless others think it's worth the effort