Same here,
I had before the update the following tests failing
testIdentifierNaming(org.hibernate.search.test.batchindexing.SearchIndexerTest)
testBatchIndexing(org.hibernate.search.test.batchindexing.IndexingGeneratedCorpusTest)
afterwards
testIdentifierNaming(org.hibernate.search.test.batchindexing.SearchIndexerTest)
--Hardy
On Thu, 03 Jun 2010 14:34:43 +0200, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
Cool
The OOME is gone.
I still see the SearchIndexerTest issue though from trunk.
On 3 juin 2010, at 14:24, Sanne Grinovero wrote:
> 2010/6/3 Emmanuel Bernard <emmanuel(a)hibernate.org>:
>> Somebody broke HSEARCH
>>
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-536
>>
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-537
>>
>> Both points to the mass indexer. Is it possible to get them fixed or
>> should we exclude them?
>
> I might have fixed the OOM (HSEARCH-536), but as it's not happening in
> my IDE I'm not sure and will wait for feedback from you.
> To be able to reproduce HSEARCH-534 I had to make a complex graph out
> of this test data, it's now loading many times all Books as different
> instances; I've reduced the testdata to a more reasonable number,
> please tell me if it's low enough. It should still be large enough to
> trigger pagination and work-splitting on different threads, which is
> the purpose.
> I'll re-enable the test if you say it's all fine.
>
> Also I can't reproduce HSEARCH-537, and as it doesn't seem a logical
> error message I believe this might be a consequence of the OOM.
>
> Cheers,
> Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev