Closed andrewlock closed 1 month ago
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).
Branch report: andrew/ci/removev-prerelease
Commit report: a3cc5d6
Test service: dd-trace-dotnet
:white_check_mark: 0 Failed, 343044 Passed, 1803 Skipped, 14h 59m 49.41s Total Time :snowflake: 1 New Flaky
RunTest
- Datadog.Trace.Security.IntegrationTests.Rcm.AspNetCore5AsmDataSecurityEnabledBlockingRequestIpOneClick
- Last Failure
Benchmarks for #5912 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored.
Summary of changes
Fix the nuget smoke tests on .NET Core 3.1
Reason for change
We had to add the prerelease flag to support testing prerelease version of the nuget, but it breaks on 3.1 which doesn't support it. Tried to find a neater way around this but got bored, and just want it to work 😅
Implementation details
Remove the flag
Test coverage
This is the test