Skip the Razor Pages diagnostic listener tests on Linux .NET Core 2.1#3140
Merged
Conversation
zacharycmontoya
approved these changes
Aug 30, 2022
lucaspimentel
approved these changes
Aug 30, 2022
This comment has been minimized.
This comment has been minimized.
andrewlock
force-pushed
the
andrew/drop-razor-pages-tests-from-21
branch
from
August 30, 2022 15:46
b4b3cf2 to
f6ce98a
Compare
This comment has been minimized.
This comment has been minimized.
…e 2.1 only. This was causing `The configured user limit (128) on the number of inotify instances has been reached` when running on Ubuntu 20.04. This only impacts .NET Core 2.1, but efforts to resolve it by reducing the number of file watchers, or increasing `fs.inotify.max_user_instances` failed, so taking the cowards way out
andrewlock
force-pushed
the
andrew/drop-razor-pages-tests-from-21
branch
from
August 30, 2022 16:46
f6ce98a to
1e0a2d5
Compare
Member
Author
Benchmarks Report 🐌Benchmarks for #3140 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 - Unknown 🤷 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 - Faster 🎉 Same allocations ✔️
|
| Benchmark | base/diff | Base Median (ns) | Diff Median (ns) | Modality |
|---|---|---|---|---|
| Benchmarks.Trace.SpanBenchmark.StartFinishSpan‑netcoreapp3.1 | 1.156 | 1,025.40 | 886.91 |
Raw results
| Branch | Method | Toolchain | Mean | StdError | StdDev | Gen 0 | Gen 1 | Gen 2 | Allocated |
|---|---|---|---|---|---|---|---|---|---|
| master | StartFinishSpan |
net472 | 1.1μs | 0.462ns | 1.79ns | 0.128 | 0 | 0 | 810 B |
| master | StartFinishSpan |
netcoreapp3.1 | 1.03μs | 0.339ns | 1.27ns | 0.0102 | 0 | 0 | 760 B |
| master | StartFinishScope |
net472 | 1.35μs | 0.495ns | 1.92ns | 0.141 | 0 | 0 | 891 B |
| master | StartFinishScope |
netcoreapp3.1 | 1.09μs | 0.382ns | 1.43ns | 0.0119 | 0 | 0 | 880 B |
| #3140 | StartFinishSpan |
net472 | 1.1μs | 0.372ns | 1.44ns | 0.128 | 0 | 0 | 810 B |
| #3140 | StartFinishSpan |
netcoreapp3.1 | 885ns | 1.39ns | 5.19ns | 0.0105 | 0 | 0 | 760 B |
| #3140 | StartFinishScope |
net472 | 1.34μs | 0.721ns | 2.7ns | 0.141 | 0 | 0 | 891 B |
| #3140 | StartFinishScope |
netcoreapp3.1 | 1.08μs | 0.564ns | 2.11ns | 0.0118 | 0 | 0 | 880 B |
Benchmarks.Trace.TraceAnnotationsBenchmark - Same speed ✔️ Same allocations ✔️
Raw results
| Branch | Method | Toolchain | Mean | StdError | StdDev | Gen 0 | Gen 1 | Gen 2 | Allocated |
|---|---|---|---|---|---|---|---|---|---|
| master | RunOnMethodBegin |
net472 | 1.5μs | 0.599ns | 2.32ns | 0.141 | 0 | 0 | 891 B |
| master | RunOnMethodBegin |
netcoreapp3.1 | 1.23μs | 0.55ns | 1.98ns | 0.0119 | 0 | 0 | 880 B |
| #3140 | RunOnMethodBegin |
net472 | 1.53μs | 0.634ns | 2.37ns | 0.141 | 0 | 0 | 891 B |
| #3140 | RunOnMethodBegin |
netcoreapp3.1 | 1.16μs | 1.06ns | 3.98ns | 0.0116 | 0 | 0 | 880 B |
Member
Author
Code Coverage Report 📊✔️ Merging #3140 into master will not change line coverage
View the full report for further details: Datadog.Trace Breakdown ✔️
The following classes have significant coverage changes.
The following classes were added in #3140:
View the full reports for further details: |
dromanol
pushed a commit
that referenced
this pull request
Aug 31, 2022
…e 2.1 only. (#3140) This was causing `The configured user limit (128) on the number of inotify instances has been reached` when running on Ubuntu 20.04. This only impacts .NET Core 2.1, but efforts to resolve it by reducing the number of file watchers, or increasing `fs.inotify.max_user_instances` failed, so taking the cowards way out
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
Skip the Razor Pages diagnostic listener tests when running on .NET Core 2.1, Linux only.
Reason for change
This was causing
The configured user limit (128) on the number of inotify instances has been reachedfor .NET Core 2.1 only, after updating the host agents to Ubuntu 20.04,Implementation details
Throwing a
SkipExceptionon Linux .NET Core 2.1. This only impacts .NET Core 2.1, but efforts to resolve it by reducing the number of file watchers, or increasingfs.inotify.max_user_instancesfailed, so taking the cowards way outTest coverage
🤞 those integration tests
Other details
Supersedes #3138