You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Peter Ansell (JIRA)" <ji...@apache.org> on 2012/05/21 02:23:41 UTC

[jira] [Created] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Peter Ansell created STANBOL-620:
------------------------------------

             Summary: Commons Solr Managed tests fail on second invocation
                 Key: STANBOL-620
                 URL: https://issues.apache.org/jira/browse/STANBOL-620
             Project: Stanbol
          Issue Type: Bug
          Components: Commons
    Affects Versions: 0.10.0-incubating
         Environment: Maven 3.0.4

OpenJDK-7

Ubuntu 12.04
            Reporter: Peter Ansell


The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:

testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)

To reproduce clear the repository cache

rm -rf ~/.m2/repository/org/apache/stanbol/

cd stanbol/commons/

mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )

mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280686#comment-13280686 ] 

Peter Ansell commented on STANBOL-620:
--------------------------------------

JUnit fix to provide deterministic test method sorting for openjdk-7, and any other jvms that switch to indeterministic method sorting, should be in junit-4.11 [1]

That should make it possible to always know that one test method will execute before another, avoiding the confusing trail of events that I went through to find the cause for this bug.

[1] https://github.com/KentBeck/junit/issues/429
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.10.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler resolved STANBOL-620.
-----------------------------------------

    Resolution: Fixed
      Assignee: Rupert Westenthaler

Stanbol now uses Junit 4.11. This release changed execution oder for unit tests. looks like that the execution order is no longer the same os the method order within the source code. Not a problem, because unit tests must not depend on each other ... but required several changes to existing tests that depended on the ordering.

fixed with http://svn.apache.org/viewvc?rev=1409748&view=rev
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.9.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>            Assignee: Rupert Westenthaler
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280753#comment-13280753 ] 

Rupert Westenthaler commented on STANBOL-620:
---------------------------------------------

Thx Peter for the detailed analysis.

As far as I know there are also a lot of other Unit Test within Stanbol that depend on the execution order. So this may affect tests of several components!

Based on [1] I assume that junit-4.11 will be released soonishâ„¢


[1] http://tech.groups.yahoo.com/group/junit/message/23898
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.10.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Reopened] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Rupert Westenthaler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rupert Westenthaler reopened STANBOL-620:
-----------------------------------------


a test on unix showed some more tests affected by the execution oder ... reopen to fix those as well
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.9.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>            Assignee: Rupert Westenthaler
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497568#comment-13497568 ] 

Peter Ansell commented on STANBOL-620:
--------------------------------------

JUnit-4.11 has now been released and is available at Maven Central.
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.9.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279910#comment-13279910 ] 

Peter Ansell commented on STANBOL-620:
--------------------------------------

After I opened up Eclipse, with M2E active, the test started consistently passing even after wiping out all /org/apache/stanbol/ artifacts

To get it to fail again I closed down Eclipse and performed the following steps to wipe out all /org/apache/ artifacts from my local maven repository, after which it failed on the first invocation, not the second!

    rm -rf ~/.m2/repository/org/apache/

    mvn clean install (testGetManagedIndexes failed with the following test report)

testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)  Time elapsed: 0.003 sec  <<< FAILURE!
junit.framework.AssertionFailedError: null
	at junit.framework.Assert.fail(Assert.java:47)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at junit.framework.Assert.assertTrue(Assert.java:27)
	at org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest.testGetManagedIndexes(ManagedSolrServerTest.java:131)
	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:601)
	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.InvokeMethod.evaluate(InvokeMethod.java:20)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
	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.runners.ParentRunner.run(ParentRunner.java:236)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
	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:601)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)

                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.10.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498299#comment-13498299 ] 

Peter Ansell commented on STANBOL-620:
--------------------------------------

If you need to fix the method order to some consistent sequence you can do so using one of the following annotations [1]:

@FixMethodOrder(MethodSorters.DEFAULT)

@FixMethodOrder(MethodSorters.NAME_ASCENDING)

You can also use any other available MethodSorters for different purposes, including the following to use the JVM order which may vary from run to run:

@FixMethodOrder(MethodSorters.JVM)

[1] https://github.com/KentBeck/junit/blob/master/doc/ReleaseNotes4.11.md
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.9.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>            Assignee: Rupert Westenthaler
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279915#comment-13279915 ] 

Peter Ansell commented on STANBOL-620:
--------------------------------------

After adding the following debugging line at the start of the for loop in testGetManagedIndexes:

            log.info("Index present: "+metadata.getIndexName());

I got the following results in the junit results:

1159 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - Index present: entityhub
1159 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - Index present: cache
1159 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - Index present: testIndexInitialisation_1337562614089

It appears that the testDefaultIndexInitialisation index is being created before testGetManagedIndexes runs, but only in some circumstances it seems. On other runs the following two lines are printed higher up in the log.

1052 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - Index present:entityhub
1052 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - Index present:cache


Is the ManagedSolrServerTest class setup incorrectly to rely on the tests being executed in a particular order? Is it possible to remove the testIndexInitialisation index to properly cleanup that test?
                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.10.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (STANBOL-620) Commons Solr Managed tests fail on second invocation

Posted by "Peter Ansell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279905#comment-13279905 ] 

Peter Ansell commented on STANBOL-620:
--------------------------------------

The logs from testing are different across the two runs, so it may be a synchronisation/asynchronous test bug:

On the first run, the following partial log appears, and there are three lines after the JUnit results are printed:

Running org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest
1 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - check ServerDir: /home/peter/gitrepos/stanbol/commons/solr/managed/target/indexes
2 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - configured SolrServer Location: ${basedir}/target/indexes
...
1172 [main] INFO org.apache.solr.search.SolrIndexSearcher - Opening Searcher@302d6b3 main
1172 [main] INFO org.apache.solr.core.SolrCore - AutoCommit: disabled
1172 [main] INFO org.apache.solr.handler.component.SpellCheckComponent - Initializing spell checkers
1174 [main] INFO org.apache.solr.spelling.AbstractLuceneSpellChecker - Using WhitespaceAnalzyer for dictionary: default
1174 [main] WARN org.apache.solr.handler.component.SpellCheckComponent - No queryConverter defined, using default converter
1174 [main] INFO org.apache.solr.handler.component.QueryElevationComponent - Loading QueryElevation from: /home/peter/gitrepos/stanbol/commons/solr/managed/target/indexes/default/testIndexInitialisation_1337560490703/conf/elevate.xml
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.QueryComponent@48879c2a
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.FacetComponent@3f1dae99
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.MoreLikeThisComponent@35b1df2e
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.HighlightComponent@30b3608c
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.StatsComponent@5087a04e
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  debug component:org.apache.solr.handler.component.DebugComponent@782d8a2f
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.QueryComponent@48879c2a
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.FacetComponent@3f1dae99
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.MoreLikeThisComponent@35b1df2e
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.HighlightComponent@30b3608c
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.StatsComponent@5087a04e
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.SpellCheckComponent@75cb514c
1177 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  debug component:org.apache.solr.handler.component.DebugComponent@782d8a2f
1178 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - QuerySenderListener sending requests to Searcher@302d6b3 main
1178 [main] INFO org.apache.solr.core.CoreContainer - registering core: testIndexInitialisation_1337560490703
1178 [main] INFO org.apache.solr.core.CoreContainer - Persisting cores config to /home/peter/gitrepos/stanbol/commons/solr/managed/target/indexes/default/solr.xml
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.218 sec
1178 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - [testIndexInitialisation_1337560490703] webapp=null path=null params={event=firstSearcher&q=static+firstSearcher+warming+in+solrconfig.xml} hits=0 status=0 QTime=0 
1178 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - QuerySenderListener done.
1178 [pool-5-thread-1] INFO org.apache.solr.handler.component.SpellCheckComponent - Loading spell index for spellchecker: default


On the second run where the test fails, the following log appears, and there are no lines from the test logger after the JUnit results are printed:

Running org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest
1 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - check ServerDir: /home/peter/gitrepos/stanbol/commons/solr/managed/target/indexes
1 [main] INFO org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest - configured SolrServer Location: ${basedir}/target/indexes
...
1147 [main] INFO org.apache.solr.search.SolrIndexSearcher - Opening Searcher@6c0037a0 main
1147 [main] INFO org.apache.solr.core.SolrCore - AutoCommit: disabled
1147 [main] INFO org.apache.solr.handler.component.SpellCheckComponent - Initializing spell checkers
1148 [main] INFO org.apache.solr.spelling.AbstractLuceneSpellChecker - Using WhitespaceAnalzyer for dictionary: default
1148 [main] WARN org.apache.solr.handler.component.SpellCheckComponent - No queryConverter defined, using default converter
1148 [main] INFO org.apache.solr.handler.component.QueryElevationComponent - Loading QueryElevation from: /home/peter/gitrepos/stanbol/commons/solr/managed/target/indexes/default/testIndexInitialisation_1337560438894/conf/elevate.xml
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.QueryComponent@759d36f1
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.FacetComponent@2482448a
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.MoreLikeThisComponent@6461d2bf
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.HighlightComponent@52532d15
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.StatsComponent@52b4e7ec
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  debug component:org.apache.solr.handler.component.DebugComponent@62e6615f
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.QueryComponent@759d36f1
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.FacetComponent@2482448a
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.MoreLikeThisComponent@6461d2bf
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.HighlightComponent@52532d15
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.StatsComponent@52b4e7ec
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  component:org.apache.solr.handler.component.SpellCheckComponent@302d6b3
1150 [main] INFO org.apache.solr.handler.component.SearchHandler - Adding  debug component:org.apache.solr.handler.component.DebugComponent@62e6615f
1151 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - QuerySenderListener sending requests to Searcher@6c0037a0 main
1151 [main] INFO org.apache.solr.core.CoreContainer - registering core: testIndexInitialisation_1337560438894
1151 [main] INFO org.apache.solr.core.CoreContainer - Persisting cores config to /home/peter/gitrepos/stanbol/commons/solr/managed/target/indexes/default/solr.xml
1151 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - [testIndexInitialisation_1337560438894] webapp=null path=null params={event=firstSearcher&q=static+firstSearcher+warming+in+solrconfig.xml} hits=0 status=0 QTime=0 
1152 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - QuerySenderListener done.
1152 [pool-5-thread-1] INFO org.apache.solr.handler.component.SpellCheckComponent - Loading spell index for spellchecker: default
1152 [pool-5-thread-1] INFO org.apache.solr.core.SolrCore - [testIndexInitialisation_1337560438894] Registered new searcher Searcher@6c0037a0 main
Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.195 sec <<< FAILURE!



There are also a number of warnings from maven-bundle-plugin that may not be relevant but look interesting:

[INFO] --- maven-bundle-plugin:2.0.1:bundle (default-bundle) @ org.apache.stanbol.commons.solr.core ---
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Instructions in Private-Package, or -testpackages that are never used: org\.apache\.stanbol\.commons\.solr\.impl, org\.apache\.stanbol\.commons\.solr\.impl\.install
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Split package org/apache/solr/analysis
Use directive -split-package:=(merge-first|merge-last|error|first) on Export/Private Package instruction to get rid of this warning
Package found in   [Jar:solr-core, Jar:solr-analysis-extras]
Reference from     /home/peter/.m2/repository/org/apache/solr/solr-analysis-extras/3.2.0/solr-analysis-extras-3.2.0.jar
Classpath          [Jar:., Jar:org.apache.stanbol.commons.stanboltools.datafileprovider, Jar:solr-solrj, Jar:geronimo-stax-api_1.0_spec, Jar:zookeeper, Jar:log4j, Jar:jline, Jar:commons-httpclient, Jar:commons-logging, Jar:lucene-xercesImpl, Jar:solr-core, Jar:solr-dataimporthandler, Jar:solr-noggit, Jar:solr-commons-csv, Jar:solr-analysis-extras, Jar:lucene-smartcn, Jar:lucene-stempel, Jar:lucene-core, Jar:lucene-analyzers, Jar:lucene-highlighter, Jar:lucene-memory, Jar:lucene-misc, Jar:lucene-queries, Jar:lucene-spellchecker, Jar:lucene-spatial, Jar:lucene-icu, Jar:lucene-icu4j, Jar:icu4j, Jar:jakarta-regexp, Jar:portlet-api, Jar:commons-codec, Jar:commons-fileupload, Jar:commons-io, Jar:commons-lang, Jar:commons-beanutils, Jar:commons-collections, Jar:xml-resolver, Jar:stax-api, Jar:wstx-asl, Jar:xalan, Jar:serializer, Jar:xml-apis, Jar:servlet-api, Jar:velocity, Jar:oro, Jar:velocity-tools, Jar:commons-digester, Jar:commons-chain, Jar:commons-validator, Jar:dom4j, Jar:sslext, Jar:struts-core, Jar:antlr, Jar:struts-taglib, Jar:struts-tiles, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:org.apache.felix.scr.annotations, Jar:org.apache.sling.installer.core, Jar:commons-compress, Jar:slf4j-api]
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Split package org/apache/lucene/index
Use directive -split-package:=(merge-first|merge-last|error|first) on Export/Private Package instruction to get rid of this warning
Package found in   [Jar:lucene-core, Jar:lucene-memory, Jar:lucene-misc]
Reference from     /home/peter/.m2/repository/org/apache/lucene/lucene-misc/3.2.0/lucene-misc-3.2.0.jar
Classpath          [Jar:., Jar:org.apache.stanbol.commons.stanboltools.datafileprovider, Jar:solr-solrj, Jar:geronimo-stax-api_1.0_spec, Jar:zookeeper, Jar:log4j, Jar:jline, Jar:commons-httpclient, Jar:commons-logging, Jar:lucene-xercesImpl, Jar:solr-core, Jar:solr-dataimporthandler, Jar:solr-noggit, Jar:solr-commons-csv, Jar:solr-analysis-extras, Jar:lucene-smartcn, Jar:lucene-stempel, Jar:lucene-core, Jar:lucene-analyzers, Jar:lucene-highlighter, Jar:lucene-memory, Jar:lucene-misc, Jar:lucene-queries, Jar:lucene-spellchecker, Jar:lucene-spatial, Jar:lucene-icu, Jar:lucene-icu4j, Jar:icu4j, Jar:jakarta-regexp, Jar:portlet-api, Jar:commons-codec, Jar:commons-fileupload, Jar:commons-io, Jar:commons-lang, Jar:commons-beanutils, Jar:commons-collections, Jar:xml-resolver, Jar:stax-api, Jar:wstx-asl, Jar:xalan, Jar:serializer, Jar:xml-apis, Jar:servlet-api, Jar:velocity, Jar:oro, Jar:velocity-tools, Jar:commons-digester, Jar:commons-chain, Jar:commons-validator, Jar:dom4j, Jar:sslext, Jar:struts-core, Jar:antlr, Jar:struts-taglib, Jar:struts-tiles, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:org.apache.felix.scr.annotations, Jar:org.apache.sling.installer.core, Jar:commons-compress, Jar:slf4j-api]
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Split package org/apache/lucene/store
Use directive -split-package:=(merge-first|merge-last|error|first) on Export/Private Package instruction to get rid of this warning
Package found in   [Jar:lucene-core, Jar:lucene-misc]
Reference from     /home/peter/.m2/repository/org/apache/lucene/lucene-misc/3.2.0/lucene-misc-3.2.0.jar
Classpath          [Jar:., Jar:org.apache.stanbol.commons.stanboltools.datafileprovider, Jar:solr-solrj, Jar:geronimo-stax-api_1.0_spec, Jar:zookeeper, Jar:log4j, Jar:jline, Jar:commons-httpclient, Jar:commons-logging, Jar:lucene-xercesImpl, Jar:solr-core, Jar:solr-dataimporthandler, Jar:solr-noggit, Jar:solr-commons-csv, Jar:solr-analysis-extras, Jar:lucene-smartcn, Jar:lucene-stempel, Jar:lucene-core, Jar:lucene-analyzers, Jar:lucene-highlighter, Jar:lucene-memory, Jar:lucene-misc, Jar:lucene-queries, Jar:lucene-spellchecker, Jar:lucene-spatial, Jar:lucene-icu, Jar:lucene-icu4j, Jar:icu4j, Jar:jakarta-regexp, Jar:portlet-api, Jar:commons-codec, Jar:commons-fileupload, Jar:commons-io, Jar:commons-lang, Jar:commons-beanutils, Jar:commons-collections, Jar:xml-resolver, Jar:stax-api, Jar:wstx-asl, Jar:xalan, Jar:serializer, Jar:xml-apis, Jar:servlet-api, Jar:velocity, Jar:oro, Jar:velocity-tools, Jar:commons-digester, Jar:commons-chain, Jar:commons-validator, Jar:dom4j, Jar:sslext, Jar:struts-core, Jar:antlr, Jar:struts-taglib, Jar:struts-tiles, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:org.apache.felix.scr.annotations, Jar:org.apache.sling.installer.core, Jar:commons-compress, Jar:slf4j-api]
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Split package org/apache/lucene/search
Use directive -split-package:=(merge-first|merge-last|error|first) on Export/Private Package instruction to get rid of this warning
Package found in   [Jar:lucene-core, Jar:lucene-highlighter, Jar:lucene-queries, Jar:lucene-spellchecker]
Reference from     /home/peter/.m2/repository/org/apache/lucene/lucene-queries/3.2.0/lucene-queries-3.2.0.jar
Classpath          [Jar:., Jar:org.apache.stanbol.commons.stanboltools.datafileprovider, Jar:solr-solrj, Jar:geronimo-stax-api_1.0_spec, Jar:zookeeper, Jar:log4j, Jar:jline, Jar:commons-httpclient, Jar:commons-logging, Jar:lucene-xercesImpl, Jar:solr-core, Jar:solr-dataimporthandler, Jar:solr-noggit, Jar:solr-commons-csv, Jar:solr-analysis-extras, Jar:lucene-smartcn, Jar:lucene-stempel, Jar:lucene-core, Jar:lucene-analyzers, Jar:lucene-highlighter, Jar:lucene-memory, Jar:lucene-misc, Jar:lucene-queries, Jar:lucene-spellchecker, Jar:lucene-spatial, Jar:lucene-icu, Jar:lucene-icu4j, Jar:icu4j, Jar:jakarta-regexp, Jar:portlet-api, Jar:commons-codec, Jar:commons-fileupload, Jar:commons-io, Jar:commons-lang, Jar:commons-beanutils, Jar:commons-collections, Jar:xml-resolver, Jar:stax-api, Jar:wstx-asl, Jar:xalan, Jar:serializer, Jar:xml-apis, Jar:servlet-api, Jar:velocity, Jar:oro, Jar:velocity-tools, Jar:commons-digester, Jar:commons-chain, Jar:commons-validator, Jar:dom4j, Jar:sslext, Jar:struts-core, Jar:antlr, Jar:struts-taglib, Jar:struts-tiles, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:org.apache.felix.scr.annotations, Jar:org.apache.sling.installer.core, Jar:commons-compress, Jar:slf4j-api]
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Split package org/apache/lucene/collation
Use directive -split-package:=(merge-first|merge-last|error|first) on Export/Private Package instruction to get rid of this warning
Package found in   [Jar:lucene-core, Jar:lucene-icu]
Reference from     /home/peter/.m2/repository/org/apache/lucene/lucene-icu/3.2.0/lucene-icu-3.2.0.jar
Classpath          [Jar:., Jar:org.apache.stanbol.commons.stanboltools.datafileprovider, Jar:solr-solrj, Jar:geronimo-stax-api_1.0_spec, Jar:zookeeper, Jar:log4j, Jar:jline, Jar:commons-httpclient, Jar:commons-logging, Jar:lucene-xercesImpl, Jar:solr-core, Jar:solr-dataimporthandler, Jar:solr-noggit, Jar:solr-commons-csv, Jar:solr-analysis-extras, Jar:lucene-smartcn, Jar:lucene-stempel, Jar:lucene-core, Jar:lucene-analyzers, Jar:lucene-highlighter, Jar:lucene-memory, Jar:lucene-misc, Jar:lucene-queries, Jar:lucene-spellchecker, Jar:lucene-spatial, Jar:lucene-icu, Jar:lucene-icu4j, Jar:icu4j, Jar:jakarta-regexp, Jar:portlet-api, Jar:commons-codec, Jar:commons-fileupload, Jar:commons-io, Jar:commons-lang, Jar:commons-beanutils, Jar:commons-collections, Jar:xml-resolver, Jar:stax-api, Jar:wstx-asl, Jar:xalan, Jar:serializer, Jar:xml-apis, Jar:servlet-api, Jar:velocity, Jar:oro, Jar:velocity-tools, Jar:commons-digester, Jar:commons-chain, Jar:commons-validator, Jar:dom4j, Jar:sslext, Jar:struts-core, Jar:antlr, Jar:struts-taglib, Jar:struts-tiles, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:org.apache.felix.scr.annotations, Jar:org.apache.sling.installer.core, Jar:commons-compress, Jar:slf4j-api]
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Instructions in Export-Package that are never used: org\.apache\.solr\.update \..*|org\.apache\.solr\.update 
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Superfluous export-package instructions: [org.apache.solr.update .*]
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Did not find matching referal for !antlr.*
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.core:bundle:0.10.0-incubating-SNAPSHOT : Did not find matching referal for !org.apache.tika.*

.....

[INFO] --- maven-bundle-plugin:2.0.1:bundle (default-bundle) @ org.apache.stanbol.commons.solr.web ---
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.web:bundle:0.10.0-incubating-SNAPSHOT : Instructions in Private-Package, or -testpackages that are never used: org\.apache\.stanbol\.commons\.solr\.web\.utils
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.web:bundle:0.10.0-incubating-SNAPSHOT : Instructions in Export-Package that are never used: org\.apache\.stanbol\.commons\.solr\.web
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.web:bundle:0.10.0-incubating-SNAPSHOT : Superfluous export-package instructions: [org.apache.stanbol.commons.solr.web]

.....

[INFO] --- maven-bundle-plugin:2.0.1:bundle (default-bundle) @ org.apache.stanbol.commons.solr.web ---
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.web:bundle:0.10.0-incubating-SNAPSHOT : Instructions in Private-Package, or -testpackages that are never used: org\.apache\.stanbol\.commons\.solr\.web\.utils
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.web:bundle:0.10.0-incubating-SNAPSHOT : Instructions in Export-Package that are never used: org\.apache\.stanbol\.commons\.solr\.web
[WARNING] Warning building bundle org.apache.stanbol:org.apache.stanbol.commons.solr.web:bundle:0.10.0-incubating-SNAPSHOT : Superfluous export-package instructions: [org.apache.stanbol.commons.solr.web]

                
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
>                 Key: STANBOL-620
>                 URL: https://issues.apache.org/jira/browse/STANBOL-620
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: 0.10.0-incubating
>         Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
>            Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install on the commons reactor after clearing the maven cache repository of all org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed when the tests passed fine the first time through)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira