[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync

2011-11-21 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/303/

1 tests failed.
REGRESSION:  org.apache.lucene.facet.taxonomy.directory.TestIndexClose.testLeaks

Error Message:
java.lang.AssertionError: Some threads threw uncaught exceptions!

Stack Trace:
java.lang.RuntimeException: java.lang.AssertionError: Some threads threw 
uncaught exceptions!
at 
org.apache.lucene.util.LuceneTestCase.tearDown(LuceneTestCase.java:650)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:37)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at 
org.apache.lucene.util.LuceneTestCaseRunner.runChild(LuceneTestCaseRunner.java:149)
at 
org.apache.lucene.util.LuceneTestCaseRunner.runChild(LuceneTestCaseRunner.java:51)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: java.lang.AssertionError: Some threads threw uncaught exceptions!
at org.junit.Assert.fail(Assert.java:91)
at 
org.apache.lucene.util.LuceneTestCase.checkUncaughtExceptionsAfter(LuceneTestCase.java:678)
at 
org.apache.lucene.util.LuceneTestCase.tearDown(LuceneTestCase.java:622)
... 30 more




Build Log (for compile errors):
[...truncated 24882 lines...]



-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync

2011-11-21 Thread Shai Erera
Perhaps it's a build error (i.e. not cleaning after the test)? This is the
exception that appears in the log:

The following exceptions were thrown by threads:
*** Thread: Lucene Merge Thread #0 ***
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
at 
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:513)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:478)
Caused by: java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
at org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)
at org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)
at 
org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)
at 
org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51)
at 
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)
at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)
at 
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)
at 
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:383)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:451)
*** Thread: Lucene Merge Thread #1 ***
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
at 
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:513)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:478)
Caused by: java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
at org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)
at org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)
at 
org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)
at 
org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51)
at 
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)
at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)
at 
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)
at 
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:383)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:451)
*** Thread: Lucene Merge Thread #2 ***
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
at 
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:513)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:478)
Caused by: java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
at org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)
at org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)
at 
org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)
at 
org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51)
at 
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)
at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)
at 
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)
at 
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:383)
at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:451)
NOTE: reproduce with: ant test -Dtestcase=TestIndexClose
-Dtestmethod=testLeaks
-Dtests.seed=78e524cead5893e3:4edf9eedd4ed0a36:1912c3654ff9f2e1
-Dargs=-Dfile.encoding=ISO8859-1
NOTE: test params are: codec=Lucene3x,
sim=RandomSimilarityProvider(queryNorm=false,coord=false):
{$full_path$=DFR I(ne)Z(0.3), $payloads$=IB LL-DZ(0.3)}, locale=et_EE,
timezone=America/Argentina/Mendoza
NOTE: all tests run in this JVM:
[TestAdaptiveExample, TestSimpleExample, TestAssociationExample,
TestMultiCLExample, TestScoredDocIDsUtils,
CategoryListPayloadStreamTest, CategoryAttributesIterableTest,
CategoryAttributeImplTest, DefaultFacetIndexingParamsTest,
CategoryListParamsTest, PerDimensionIndexingParamsTest,

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync

2011-11-21 Thread Steven A Rowe
I wasn’t able to reproduce using Ant.

But I can consistently reproduce the failure with both of these Maven cmdlines 
under modules/facet/:

mvn 
-Dtests.seed=78e524cead5893e3:4edf9eedd4ed0a36:1912c3654ff9f2e1 
-Dtest=TestIndexClose clean test

mvn -Dtests.codec=Lucene3x -Dtest=TestIndexClose clean test

Without specifying -Dtests.codec or -Dtests.seed, “mvn clean test” usually 
succeeds; it looks like this is specific to the Lucene3x codec under Maven.

I ran all Lucene/Solr tests under Maven with “-Dtests.codec=Lucene3x” (using 
mvn’s --fail-at-end option), and the facet module’s TextIndexClose is the only 
failing test.

Maybe there is a Maven-specific test classpath ordering problem here?

Steve

From: Shai Erera [mailto:ser...@gmail.com]
Sent: Monday, November 21, 2011 11:13 AM
To: dev@lucene.apache.org
Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync

Perhaps it's a build error (i.e. not cleaning after the test)? This is the 
exception that appears in the log:



The following exceptions were thrown by threads:

*** Thread: Lucene Merge Thread #0 ***

org.apache.lucene.index.MergePolicy$MergeException: 
java.lang.IllegalStateException: sub-readers have different 
BytesRef.Comparators; cannot merge

  at 
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:513)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:478)

Caused by: java.lang.IllegalStateException: sub-readers have different 
BytesRef.Comparators; cannot merge

  at org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)

  at org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)

  at 
org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)

  at 
org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51)

  at 
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)

  at 
org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)

  at 
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)

  at 
org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:383)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:451)

*** Thread: Lucene Merge Thread #1 ***

org.apache.lucene.index.MergePolicy$MergeException: 
java.lang.IllegalStateException: sub-readers have different 
BytesRef.Comparators; cannot merge

  at 
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:513)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:478)

Caused by: java.lang.IllegalStateException: sub-readers have different 
BytesRef.Comparators; cannot merge

  at org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)

  at org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)

  at 
org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)

  at 
org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51)

  at 
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)

  at 
org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)

  at 
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)

  at 
org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:383)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:451)

*** Thread: Lucene Merge Thread #2 ***

org.apache.lucene.index.MergePolicy$MergeException: 
java.lang.IllegalStateException: sub-readers have different 
BytesRef.Comparators; cannot merge

  at 
org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:513)

  at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:478)

Caused by: java.lang.IllegalStateException: sub-readers have different 
BytesRef.Comparators; cannot merge

  at org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)

  at org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)

  at 
org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)

  at 
org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51)

  at 
org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync

2011-11-21 Thread Steven A Rowe
I tried this, and the test fails under Maven; codec's class is 
o.a.l.index.codecs.lucene3x.Lucene3xCodec instead of 
o.a.l.index.codecs.preflexrw.PreFlexRWCodec.

So, it's a classpath ordering issue.  I'll see if I can do some re-ordering.

Steve

 -Original Message-
 From: Steven A Rowe [mailto:sar...@syr.edu]
 Sent: Monday, November 21, 2011 2:40 PM
 To: dev@lucene.apache.org
 Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
 sync
 
 Thanks, I'll give it a try. - Steve
 
  -Original Message-
  From: Robert Muir [mailto:rcm...@gmail.com]
  Sent: Monday, November 21, 2011 2:38 PM
  To: dev@lucene.apache.org
  Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
  sync
 
  If you want to confirm thats the bug, just add a test to this contrib
  module that looks like TestImpersonation:
 
  public class TestImpersonation extends LuceneTestCase {
public void test() throws Exception {
  Codec codec = Codec.forName(Lucene3x);
  assertTrue(codec instanceof PreFlexRWCodec);
}
  }
 
  On Mon, Nov 21, 2011 at 2:35 PM, Uwe Schindler u...@thetaphi.de wrote:
   Exactly, test-framework must come before core.
  
   The reason here is that 3x impersonation does not work.
  
   Uwe
   --
   Uwe Schindler
   H.-H.-Meier-Allee 63, 28213 Bremen
   http://www.thetaphi.de
  
  
  
   Steven A Rowe sar...@syr.edu schrieb:
  
   I wasn’t able to reproduce using Ant.
  
  
  
   But I can consistently reproduce the failure with both of these Maven
   cmdlines under modules/facet/:
  
  
  
       mvn
   -Dtests.seed=78e524cead5893e3:4edf9eedd4ed0a36:1912c3654ff9f2e1
   -Dtest=TestIndexClose clean test
  
  
  
   mvn -Dtests.codec=Lucene3x -Dtest=TestIndexClose clean test
  
  
  
   Without specifying -Dtests.codec or -Dtests.seed, “mvn clean test”
  usually
   succeeds; it looks like this is specific to the Lucene3x codec under
  Maven.
  
  
  
   I ran all Lucene/Solr tests under Maven with “-Dtests.codec=Lucene3x”
   (using mvn’s --fail-at-end option), and the facet module’s
  TextIndexClose is
   the only failing test.
  
  
  
   Maybe there is a Maven-specific test classpath ordering problem here?
  
  
  
   Steve
  
  
  
   From: Shai Erera [mailto:ser...@gmail.com]
   Sent: Monday, November 21, 2011 11:13 AM
   To: dev@lucene.apache.org
   Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out
 of
   sync
  
  
  
   Perhaps it's a build error (i.e. not cleaning after the test)? This
 is
  the
   exception that appears in the log:
  
  
  
   The following exceptions were thrown by threads:
  
   *** Thread: Lucene Merge Thread #0 ***
  
   org.apache.lucene.index.MergePolicy$MergeException:
   java.lang.IllegalStateException: sub-readers have different
   BytesRef.Comparators; cannot merge
  
     at
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(Conc
  urrentMergeScheduler.java:513)
  
     at
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurren
  tMergeScheduler.java:478)
  
   Caused by: java.lang.IllegalStateException: sub-readers have
 different
   BytesRef.Comparators; cannot merge
  
     at
   org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)
  
     at
   org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)
  
     at
  
 org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)
  
     at
  
 
 org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51
  )
  
     at
  
  org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)
  
     at
   org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)
  
     at
  
 org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)
  
     at
   org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)
  
     at
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeSc
  heduler.java:383)
  
     at
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurren
  tMergeScheduler.java:451)
  
   *** Thread: Lucene Merge Thread #1 ***
  
   org.apache.lucene.index.MergePolicy$MergeException:
   java.lang.IllegalStateException: sub-readers have different
   BytesRef.Comparators; cannot merge
  
     at
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(Conc
  urrentMergeScheduler.java:513)
  
     at
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurren
  tMergeScheduler.java:478)
  
   Caused by: java.lang.IllegalStateException: sub-readers have
 different
   BytesRef.Comparators; cannot merge
  
     at
   org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)
  
     at
   org.apache.lucene.index.MultiFields.terms(MultiFields.java:232

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of sync

2011-11-21 Thread Steven A Rowe
I committed a fix for all modules' POMs in r1204732.  All tests pass for me 
locally (except for benchmark module's LineDocSourceTest: LUCENE-3583).

 -Original Message-
 From: Steven A Rowe [mailto:sar...@syr.edu]
 Sent: Monday, November 21, 2011 3:47 PM
 To: dev@lucene.apache.org
 Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
 sync
 
 I tried this, and the test fails under Maven; codec's class is
 o.a.l.index.codecs.lucene3x.Lucene3xCodec instead of
 o.a.l.index.codecs.preflexrw.PreFlexRWCodec.
 
 So, it's a classpath ordering issue.  I'll see if I can do some re-
 ordering.
 
 Steve
 
  -Original Message-
  From: Steven A Rowe [mailto:sar...@syr.edu]
  Sent: Monday, November 21, 2011 2:40 PM
  To: dev@lucene.apache.org
  Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
  sync
 
  Thanks, I'll give it a try. - Steve
 
   -Original Message-
   From: Robert Muir [mailto:rcm...@gmail.com]
   Sent: Monday, November 21, 2011 2:38 PM
   To: dev@lucene.apache.org
   Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out of
   sync
  
   If you want to confirm thats the bug, just add a test to this contrib
   module that looks like TestImpersonation:
  
   public class TestImpersonation extends LuceneTestCase {
 public void test() throws Exception {
   Codec codec = Codec.forName(Lucene3x);
   assertTrue(codec instanceof PreFlexRWCodec);
 }
   }
  
   On Mon, Nov 21, 2011 at 2:35 PM, Uwe Schindler u...@thetaphi.de
 wrote:
Exactly, test-framework must come before core.
   
The reason here is that 3x impersonation does not work.
   
Uwe
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
   
   
   
Steven A Rowe sar...@syr.edu schrieb:
   
I wasn’t able to reproduce using Ant.
   
   
   
But I can consistently reproduce the failure with both of these
 Maven
cmdlines under modules/facet/:
   
   
   
    mvn
-Dtests.seed=78e524cead5893e3:4edf9eedd4ed0a36:1912c3654ff9f2e1
-Dtest=TestIndexClose clean test
   
   
   
mvn -Dtests.codec=Lucene3x -Dtest=TestIndexClose clean test
   
   
   
Without specifying -Dtests.codec or -Dtests.seed, “mvn clean test”
   usually
succeeds; it looks like this is specific to the Lucene3x codec
 under
   Maven.
   
   
   
I ran all Lucene/Solr tests under Maven with “-
 Dtests.codec=Lucene3x”
(using mvn’s --fail-at-end option), and the facet module’s
   TextIndexClose is
the only failing test.
   
   
   
Maybe there is a Maven-specific test classpath ordering problem
 here?
   
   
   
Steve
   
   
   
From: Shai Erera [mailto:ser...@gmail.com]
Sent: Monday, November 21, 2011 11:13 AM
To: dev@lucene.apache.org
Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #303: POMs out
  of
sync
   
   
   
Perhaps it's a build error (i.e. not cleaning after the test)? This
  is
   the
exception that appears in the log:
   
   
   
The following exceptions were thrown by threads:
   
*** Thread: Lucene Merge Thread #0 ***
   
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge
   
  at
   
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(Conc
   urrentMergeScheduler.java:513)
   
  at
   
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurren
   tMergeScheduler.java:478)
   
Caused by: java.lang.IllegalStateException: sub-readers have
  different
BytesRef.Comparators; cannot merge
   
  at
org.apache.lucene.index.MultiTerms.init(MultiTerms.java:55)
   
  at
org.apache.lucene.index.MultiFields.terms(MultiFields.java:232)
   
  at
   
  org.apache.lucene.index.MultiFieldsEnum.terms(MultiFieldsEnum.java:114)
   
  at
   
  
 
 org.apache.lucene.index.codecs.FieldsConsumer.merge(FieldsConsumer.java:51
   )
   
  at
   
  
 org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:293)
   
  at
org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:122)
   
  at
   
  org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3581)
   
  at
org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3215)
   
  at
   
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeSc
   heduler.java:383)
   
  at
   
  
 
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurren
   tMergeScheduler.java:451)
   
*** Thread: Lucene Merge Thread #1 ***
   
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.IllegalStateException: sub-readers have different
BytesRef.Comparators; cannot merge