-
Notifications
You must be signed in to change notification settings - Fork 150
Test against net462 to fix code coverage
#3520
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
Conversation
Datadog ReportBranch report: ❄️ New Flaky Tests (2)
|
This comment has been minimized.
This comment has been minimized.
Code Coverage Report 📊✔️ Merging #3520 into master will will increase line coverage by
View the full report for further details: Datadog.Trace Breakdown ✔️
The following classes have significant coverage changes.
The following classes were added in #3520:
View the full reports for further details: |
48d23cb to
9f283af
Compare
Benchmarks Report 🐌Benchmarks for #3520 compared to master:
The following thresholds were used for comparing the benchmark speeds:
Allocation changes below 0.5% are ignored. Benchmark detailsBenchmarks.Trace.AgentWriterBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.AppSecBodyBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.AspNetCoreBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.DbCommandBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.ElasticsearchBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.GraphQLBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.HttpClientBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.ILoggerBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.Log4netBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.NLogBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.RedisBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.SerilogBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.SpanBenchmark - Same speed ✔️ Same allocations ✔️Raw results
Benchmarks.Trace.TraceAnnotationsBenchmark - Same speed ✔️ Same allocations ✔️Raw results
|
gleocadie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
shurivich
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
robertpi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Summary of changes
net462instead ofnet461Reason for change
In #3482, after updating to the .NET 7 SDK, we had to disable code coverage when running on .NET FX, as incompatibilities meant the tests weren't running at all. To fix these issues, we need to update to the latest Microsoft.NET.Test.Sdk package version. Unfortunately, this doesn't support
net461,netcoreapp2.1, ornetcoreapp3.0.Implementation details
To avoid dropping support for
netcoreapp2.1andnetcoreapp3.0did several thingsnet462instead ofnet461net462, use the newer packagenetcoreapp2.1etc)net462onlyTest coverage
Should have the same level of coverage, but as we can now enable code coverage for .NET Framework again, the reported numbers will likely change a bit
Other details
I had to install the .NET Framework 4.6.2 targeting pack on the Windows VMs. Note that you may need to install this with Visual Studio too (I updated the .vsconfig file appropriately)