accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1255) Occasional errors in vfs2 unit tests
Date Tue, 09 Apr 2013 22:58:15 GMT

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

Dave Marion commented on ACCUMULO-1255:
---------------------------------------

reproduced. I think it's a timing issue. We had similar issues with the old classloader tests.
I'm ok with removing this test as it does not test the Accumulo class loader, its a test of
the VfsClassLoader. I was using it to understand how the api worked and to confirm that it
would pick up modifications.
                
> Occasional errors in vfs2 unit tests
> ------------------------------------
>
>                 Key: ACCUMULO-1255
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1255
>             Project: Accumulo
>          Issue Type: Bug
>          Components: start
>            Reporter: Christopher Tubbs
>            Assignee: John Vines
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> {code}
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.accumulo.start.classloader.vfs.AccumuloVFSClassLoaderTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.186 sec
> Running org.apache.accumulo.start.classloader.vfs.AccumuloReloadingVFSClassLoaderTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.218 sec
> Running org.apache.accumulo.start.classloader.vfs.providers.ReadOnlyHdfsFileProviderTest
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.654 sec
> Running org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 13.984 sec <<<
FAILURE!
> testFileMonitor(org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest)
 Time elapsed: 6.306 sec  <<< FAILURE!
> java.lang.AssertionError
> 	at org.junit.Assert.fail(Assert.java:86)
> 	at org.junit.Assert.assertTrue(Assert.java:41)
> 	at org.junit.Assert.assertTrue(Assert.java:52)
> 	at org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest.testFileMonitor(VfsClassLoaderTest.java:93)
> 	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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> 	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> 	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:189)
> 	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> 	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Running org.apache.accumulo.start.classloader.vfs.ContextManagerTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.211 sec
> Results :
> Failed tests:   testFileMonitor(org.apache.accumulo.start.classloader.vfs.providers.VfsClassLoaderTest)
> Tests run: 23, Failures: 1, Errors: 0, Skipped: 0
> {code}

--
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

Mime
View raw message