Affects Version/s: 5.0
Linux sauron 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
AMD Phenom(tm) II X3 705e, 2.5Ghz
Lucene Fields:New, Patch Available
The tests labelled @Monster are having a very hard time passing. Initially, there were some real failures on tests that push the 2 billion envelope, as well as some test bugs regarding suite timeouts and the quantity of date sent to sysout. Michael McCandless committed a fix for the real failures and the initial sysout problems.
Trying to move @SuppressSysoutChecks to the definition of @Monster didn't work. I'm also having trouble defining the suite timeouts. One test that says it takes about 45 minutes hit the six hour timeout that I had configured for the suite, and failed.
What sort of machine should we use as a "normal" machine for deciding on suite timeouts? My machine is over four years old, but it's got three 2.5Ghz cores and 12GB of RAM. That's certainly not a completely modern machine, but it's not exactly slow.