Too many open files when running dotnet test (xunit)
See original GitHub issueOriginal issue here: https://github.com/xunit/xunit/issues/874
I was able to work around this by setting ulimit -n 512
in my shell before running – but that really should not be required.
Steps to reproduce
Run the attached tests tests.zip
Expected behavior
The tests run and succeed
Actual behavior
Too many open files exception is thrown and dotnet test crashes.
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview2-003121)
Product Information:
Version: 1.0.0-preview2-003121
Commit SHA-1 hash: 1e9d529bc5
Runtime Environment:
OS Name: Mac OS X
OS Version: 10.11
OS Platform: Darwin
RID: osx.10.11-x64
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Too many open files when running dotnet test (xunit) #6560
Too many open files exception is thrown and dotnet test crashes. Environment data. dotnet --info output: .NET Command Line Tools (1.0.0-preview2 ...
Read more >Too many open files error when running go test in github ...
The error says you are running into a limit for open file descriptors, so you need to figure where you are not releasing...
Read more >[Solved] Dotnet core: kestrel hangs, Too many open files in ...
Increase the maximum number of open files for the system and for each process. Resolve the CLOSE_WAIT problem . 1- Increase the maximum...
Read more >.NET Core 2.1 - "Too Many Open Files In System" : r/dotnet
For the last few months, we have been getting a "Too Many Open Files In System" about every 7 days for our .NET...
Read more >Configure unit tests by using a .runsettings file
Learn how to use the .runsettings file in Visual Studio to configure unit tests that are run from the command line, from the...
Read more >
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
Can confirm the issue.
@eamodio Thanks for workaround
Closing for lack of activity and new information. The test tooling has changed drastically since then. If this is still an issue, please file a new bug with repro steps for us to investigate it further.