I've run that test successfully, when reducing the actual size of the "huge file" by a factor of 4, IIRC. I believe that the exception is simply what it indicates and not an issue with the code. I.e., adding more system memory or increasing virtual memory and running the test overnight would see it succeed.
On Sat, Aug 16, 2008 at 2:48 PM, Digy <[EMAIL PROTECTED]> wrote: > It fails in one minute with an OutOfMemoryException. I don't like to run > that test, since all of the running programs are swapped out. > > DIGY > > -----Original Message----- > From: Granroth, Neal V. [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 16, 2008 7:52 PM > To: [email protected] > Subject: RE: Failing unit tests > > Doug, > > The PC I used to build and run the unit-tests is a Windows XP SP2, 1GB RAM, > Pentium IV (with Hyper Threading). > The development environment is Visual Studio 2005. > > I had run the unit-tests a couple times with the same result, at least once > with no other applications running and > with the virus scanner prohibited from active scanning. > > Do you have an idea of how long the "huge file" test should take to > complete? > If it should complete in under 30 minutes than it too is failing. > > Neal > > ________________________________________ > From: Doug Sale [EMAIL PROTECTED] > Sent: Friday, August 15, 2008 9:46 AM > To: [email protected] > Subject: Re: Failing unit tests > > Neal, > > Issue (1) is strange to me. I've pulled the code from HEAD after the > latest > commits and not had a problem building (the mentioned files were present). > I believe the correct solution file to use is Test.sln. Perhaps that is > the > issue? It is a VS 2005 compatible solution. > > Regarding the errors/test faillures: We are currently working on the > errors. Any support/insight you could provide would be welcomed! There > will be announcement on the lucene-net list when 2.3.1 is officially > released. > > Thanks, > Doug > >
