From: Itamar Syn-H. <it...@co...> - 2010-08-16 22:22:54
|
Borek, the intensive_testing branch is consistently crashing in one of the IndexSearcher tests, with an AV / buffer overrun. I'm testing with VC8. Is it something you have seen already? Since it seems to be related to threading, I merged master and then atomicthreads with your branch to see if that will resolve the issue, but it didn't. You can find it under 'intensive_testing_merged'. Let me know what you find. Itamar On 15/8/2010 1:39 AM, Kostka Bořivoj wrote: > I made few additional changes in RAMDirectory.cpp and MockRAMDirectory.cpp (see intensive_testing branch for details) > Now TestRAMDirectory works fine with MockRAMDirectory. > > Veit, thanks again for your support and comments > > Borek > > >> -----Original Message----- >> From: Kostka Bořivoj [mailto:ko...@to...] >> Sent: Saturday, August 14, 2010 11:47 PM >> To: clu...@li... >> Subject: Re: [CLucene-dev] RAMDirectory testing (using MockRAMDirectory) >> >> Hi Veit, >> >> Good catch, it works fine now, thanks. >> >> Borek >> >> >>> -----Original Message----- >>> From: Kostka Bořivoj [mailto:ko...@to...] >>> Sent: Thursday, August 12, 2010 10:31 AM >>> To: clu...@li... >>> Subject: Re: [CLucene-dev] RAMDirectory testing (using MockRAMDirectory) >>> >>> Thanks, I'll apply and test >>> >>> Borek >>> >>> >>>> -----Original Message----- >>>> From: Veit Jahns [mailto:nun...@go...] >>>> Sent: Thursday, August 12, 2010 8:56 AM >>>> To: clu...@li... >>>> Subject: Re: [CLucene-dev] RAMDirectory testing (using MockRAMDirectory) >>>> >>>> 2010/8/11 Veit Jahns<nun...@go...>: >>>> >>>>> 2010/8/11 Kostka Bořivoj<ko...@to...>: >>>>> >>>>>>>> 2) MockRAMDirectory::close always throws an exception because >>>>>>>> segments.gen is in list of open files, no idea if this is a bug in >>>>>>>> RAMDirectory or MockRAMDirectory >>>>>>>> >>>>>>> Why do you use MockRAMDirectory here? I ported this class from >>>>>>> JLucene, because I needed once a directory implementation that >>>>>>> intentionally throws exceptions. And because the close-methods of >>>>>>> RAMDirectory and MockRAMDirectory are identical to the JLucene >>>>>>> methods, I'd say that's neither a bug of RAMDirectory nor MockRAMDirectory. >>>>>>> >>>>>> I use MockRAMDirectory just because it is used in original java test >>>>>> I ported. It is used in many tests in test/index folder so I wanted >>>>>> to test MockRAMDirectory itself before using it in other tests. >>>>>> >>>>> You are right. Something is odd there. I will take a close look tomorrow. >>>>> >>>> The Bug seems to be in SegmentInfos.cpp. In some case the open generation file >>>> >>> will >>> >>>> not be closed (diff attached). >>>> >>>> Veit >>>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> _______________________________________________ >>> CLucene-developers mailing list >>> CLu...@li... >>> https://lists.sourceforge.net/lists/listinfo/clucene-developers >>> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> CLucene-developers mailing list >> CLu...@li... >> https://lists.sourceforge.net/lists/listinfo/clucene-developers >> > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > CLucene-developers mailing list > CLu...@li... > https://lists.sourceforge.net/lists/listinfo/clucene-developers > > > |