Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
16.3.0 is 2.7-3.5x slower than 16.3.0-preview-20190828-03 on Windows only
See original GitHub issueMicrosoft.NET.Test.Sdk 16.3.0 is 2.7-3.5x slower than any other previous version including 16.3.0-preview-20190828-03
This is not #2120 since I can’t repro it on Linux, only on Windows.
Repro
- Use Windows and .NET Core SDK 3.0.100
- clone https://github.com/0xd4d/iced.git
- dotnet build -c Release
- dotnet test -c Release -f netcoreapp3.0 --no-build Iced.UnitTests/Iced.UnitTests.csproj
- git clean -xdf
- edit
Iced.UnitTests/Iced.UnitTests.csprojand changeMicrosoft.NET.Test.Sdkversion to16.3.0 - dotnet build -c Release
- dotnet test -c Release -f netcoreapp3.0 --no-build Iced.UnitTests/Iced.UnitTests.csproj
Notes:
- It repros on Windows, not Linux
- It only repros with 16.3.0, but not 16.3.0-preview-20190828-03 or any other previous version
| Version | Time | GitHub Actions logs |
|---|---|---|
| 16.3.0 | 4.0954 Minutes | https://github.com/0xd4d/iced/runs/249788558#step:3:48 |
| 16.3.0-preview-20190828-03 | 1.5096 Minutes | https://github.com/0xd4d/iced/runs/249798345#step:3:48 |
It’s 3.5x slower when I build it on my own machine.
Getting logs failed:
The active test run was aborted. Reason: Test host process crashed
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (7 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@0xd4d I guess you hit the bull’s eye. @vitek-karas Thanks a lot for helping out with the investigations.
@vagisha-nidhi Let’s update your PR with the discussed changes and that should take care of all the scenarios.
This might also be related to #2189.