On 10/4/2014 3:30 AM, Michael McCandless wrote: > OK I committed fixes for the monster tests. They were all trying to > add Integer.MAX_VALUE docs, but should use IndexWriter.MAX_DOCS > instead. > > I verified the change at least compiles, but didn't run all the monster > tests...
Naturally, we have new problems after these fixes. Should I open an issue for these problems, or just go ahead and commit fixes? Test2BBinaryDocValues -- too much sysout Test2BSortedDocValues -- too much sysout Test2BNumericDocValues -- too much sysout Test2BTerms -- suite timeout Test2BTerms has a 6 hour suite timeout. Some of the other monster tests have the suite timeout set to EIGHTY hours. I can understand that some tests take a long time, but that's more than three days. I'll patch these problems locally, see if things pass, and ask if anyone has a recommendation for a new suite timeout on Test2BTerms. I'm trying 12 hours to start. I'm running with tests.heapsize=6g and two JVMs, on an Ubuntu 14 server with "AMD Phenom(tm) II X3 705e" for the processor (three 2.5 Ghz cores) and 12GB of RAM. It looks like this combo has pushed me into swap, something I had hoped wouldn't happen... so I'll reduce the max heap a little bit and hope it's still enough, and look at the test log to see if Test2BTerms actually does need a larger timeout. I might need to run with only one JVM. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
