On Thu, May 31, 2012 at 8:05 PM, Robert Muir rcm...@gmail.com wrote:
On Thu, May 31, 2012 at 5:51 PM, Michael McCandless
luc...@mikemccandless.com wrote:
I think the best option is to ignore the OOME from this test case...?
Mike McCandless
I think thats fine for now, but I'm not convinced
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2723/
1 tests failed.
REGRESSION: org.apache.lucene.util.packed.TestPackedInts.testIntOverflow
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at
: Apache Jenkins Server [mailto:jenk...@builds.apache.org]
Sent: Thursday, May 31, 2012 2:55 PM
To: dev@lucene.apache.org
Subject: [JENKINS] Lucene-Solr-tests-only-trunk-java7 - Build # 2723 - Failure
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2723/
1 tests failed
This test intentionally allocates ~256 MB packed ints ... the seed
doesn't fail in isolation, but I think the test fails if it's run with
other tests that leave too much uncollectible stuff allocated in the
heap ...
Can we somehow mark that a test should be run in isolation (it's own
new JVM)...?
This test intentionally allocates ~256 MB packed ints ... the seed
doesn't fail in isolation, but I think the test fails if it's run with
other tests that leave too much uncollectible stuff allocated in the
heap ...
It doesn't need to be hard refs. With parallel garbage collectors
(with
On Thu, May 31, 2012 at 5:16 PM, Dawid Weiss
dawid.we...@cs.put.poznan.pl wrote:
This test intentionally allocates ~256 MB packed ints ... the seed
doesn't fail in isolation, but I think the test fails if it's run with
other tests that leave too much uncollectible stuff allocated in the
heap
On Thu, May 31, 2012 at 5:51 PM, Michael McCandless
luc...@mikemccandless.com wrote:
I think the best option is to ignore the OOME from this test case...?
Mike McCandless
I think thats fine for now, but I'm not convinced there is no problem
at all. However, its not obvious the problem is us,
Aaahhh... I thought G1 will start causing issues at some point. Good
catch, Robert.
Dawid
On Fri, Jun 1, 2012 at 2:05 AM, Robert Muir rcm...@gmail.com wrote:
On Thu, May 31, 2012 at 5:51 PM, Michael McCandless
luc...@mikemccandless.com wrote:
I think the best option is to ignore the OOME from