[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068213#comment-13068213
 ] 

Tobias Rübner commented on CONNECTORS-223:
------------------------------------------

I looked in the documentation of the maven surefire plugin, which executes the 
tests.
Per default, maven also runs the tests in a separate process.
The execution procedure is sequential. Each tests runs to the whole lifecycle, 
before an other test starts.  

I synced with the repository and run the tests again.
Now I get a timeout exception (I also tried a larger values).

Here is the error stack trace:
{code}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.manifoldcf.filesystem_tests.ExpirationTest
Configuration file successfully read
2011-07-20 09:26:50.333:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
2011-07-20 09:26:50.385:INFO::jetty-6.1.26
2011-07-20 09:26:50.436:INFO::Extract 
../../framework/dist/web/war/mcf-crawler-ui.war to 
/tmp/Jetty_0_0_0_0_8346_mcf.crawler.ui.war__mcf.crawler.ui__b94r7w/webapp
2011-07-20 09:26:51.565:INFO::Extract 
../../framework/dist/web/war/mcf-authority-service.war to 
/tmp/Jetty_0_0_0_0_8346_mcf.authority.service.war__mcf.authority.service__.3vgkks/webapp
2011-07-20 09:26:52.237:INFO::Extract 
../../framework/dist/web/war/mcf-api-service.war to 
/tmp/Jetty_0_0_0_0_8346_mcf.api.service.war__mcf.api.service__.67gzyk/webapp
2011-07-20 09:26:52.953:INFO::Started [email protected]:8346
2011-07-20 09:29:39.757:INFO::Stopped [email protected]:8346
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 176.237 sec
Running org.apache.manifoldcf.filesystem_tests.APISanityTest
Configuration file successfully read
2011-07-20 09:29:43.742:INFO::jetty-6.1.26
2011-07-20 09:29:43.747:INFO::Extract 
../../framework/dist/web/war/mcf-crawler-ui.war to 
/tmp/Jetty_0_0_0_0_8346_mcf.crawler.ui.war__mcf.crawler.ui__b94r7w/webapp
2011-07-20 09:29:44.798:INFO::Extract 
../../framework/dist/web/war/mcf-authority-service.war to 
/tmp/Jetty_0_0_0_0_8346_mcf.authority.service.war__mcf.authority.service__.3vgkks/webapp
2011-07-20 09:29:45.422:INFO::Extract 
../../framework/dist/web/war/mcf-api-service.war to 
/tmp/Jetty_0_0_0_0_8346_mcf.api.service.war__mcf.api.service__.67gzyk/webapp
2011-07-20 09:29:46.086:INFO::Started [email protected]:8346
org.apache.manifoldcf.core.interfaces.ManifoldCFException: ManifoldCF did not 
terminate in the allotted time of 180000 milliseconds
        at 
org.apache.manifoldcf.filesystem_tests.APISanityTest.waitJobInactive(APISanityTest.java:386)
        at 
org.apache.manifoldcf.filesystem_tests.APISanityTest.sanityCheck(APISanityTest.java:225)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
        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.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:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        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:172)
        at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
{code}

> Tests in project hierarchy do not adhere to maven conventions
> -------------------------------------------------------------
>
>                 Key: CONNECTORS-223
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.3
>
>         Attachments: CONNECTORS-223.patch, test_reset.patch
>
>
> Maven expects unit tests under .../src/test/java, and root-level project 
> tests under tests/xxx/src/test/java (or equivalent, along with their own 
> pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
> build except in location detail.  The proposal is to move stuff around to 
> make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to