nunit-core team mailing list archive

[Eberhard Beilharz <993247@xxxxxxxxxxxxxxxxxx>]

@Jv: I know how to increase the max number of file descriptors and how
to find out the number of open files under Linux.

However, I think it's pretty bad if you have tests that open a file, do
something and then close the file again and you get that "too many open
files" exception. For me that smells pretty heavily. If I run a test and
the test is implemented correctly the environment should be in the same
state afterwards as it was before. Otherwise we might run into problems
if we run a test in NUnit GUI multiple times - it will suddenly behave
differently.

And while I know how to increase the max number of file descriptors, not
everyone on my team knows that or needs to know - the tool should be
implemented correctly.

Increasing the max number of file descriptors is a workaround but it
can't be the solution - unless we really need > 1000 files open at a
time.

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/993247

Title:
  Tests fail with IOException: Too many open files

Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  When I run the unit tests of our project on Linux they fail with an
  IOException: Too many open files. The tests work fine on Windows, and
  they work if I run them fixture by fixture, or if I run them in the
  GUI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/993247/+subscriptions