You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Julia Wang (QIUHE)" <Qi...@microsoft.com> on 2014/12/03 08:54:46 UTC
Test failures in WAKE
There are test failures when build/run test on WAKE. This is from master branch. Do you have the same issue?
C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
Results :
Tests in error:
RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285 ╗ TransportRuntime
RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285 ╗ TransportRuntime
Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] REEF Wake Project ................................. SUCCESS [1.063s]
[INFO] REEF Wake ......................................... FAILURE [51.698s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 53.027s
[INFO] Finished at: Tue Dec 02 23:50:28 PST 2014
[INFO] Final Memory: 16M/255M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project wake: There are test failures.
[ERROR]
[ERROR] Please refer to C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :wake
Re: Test failures in WAKE
Posted by Markus Weimer <ma...@weimo.de>.
Hi,
I also experience intermittent test failures when I am on the
corporate network here. It all goes away when unplugging or when on
another network. When I see the tests fail, it is usually because some
port could not be opened. Hence, I am inclined to say we have a
problem with the robustness of our tests to that situation.
Markus
On 2014-12-03 03:09, Byung-Gon Chun wrote:
> I ran tests at Mac and Linux successfully.
>
> Are you running the tests in your home network behind a DSL modem?
>
>
> On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE)
> <Qiuhe.Wang@microsoft.com
>> wrote:
>
>> There are test failures when build/run test on WAKE. This is from
>> master branch. Do you have the same issue?
>>
>> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean
>> install
>>
>> Results :
>>
>> Tests in error:
>>
>> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285
>>
>>
╗ TransportRuntime
>>
>> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285
>>
>>
╗ TransportRuntime
>>
>> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>>
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
[INFO] Reactor Summary:
>> [INFO] [INFO] REEF Wake Project .................................
>> SUCCESS [1.063s] [INFO] REEF Wake
>> ......................................... FAILURE [51.698s]
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
[INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
[INFO] Total time: 53.027s
>> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014 [INFO] Final
>> Memory: 16M/255M [INFO]
>> ------------------------------------------------------------------------
>>
>>
[ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.17:test
>> (default-test) on project wake: There are test failures. [ERROR]
>> [ERROR] Please refer to
>> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports
>>
>>
for the individual test results.
>> [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace
>> of the errors, re-run Maven with the -e switch. [ERROR] Re-run
>> Maven using the -X switch to enable full debug logging. [ERROR]
>> [ERROR] For more information about the errors and possible
>> solutions, please read the following articles: [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>>
[ERROR]
>> [ERROR] After correcting the problems, you can resume the build
>> with the command [ERROR] mvn <goals> -rf :wake
>>
>
>
>
Re: Test failures in WAKE
Posted by Byung-Gon Chun <bg...@gmail.com>.
The issue is registered: https://issues.apache.org/jira/browse/REEF-68.
On Fri, Dec 5, 2014 at 7:09 AM, Byung-Gon Chun <bg...@gmail.com> wrote:
> Thanks for letting me know. This is a minor problem. Nonetheless, it's
> good to make Wake tests robust to port conflicts. I will file an issue.
>
> On Fri, Dec 5, 2014 at 2:52 AM, Julia Wang (QIUHE) <
> Qiuhe.Wang@microsoft.com> wrote:
>
>> The two test failures are about port conflict on 9000.
>>
>>
>>
>> RemoteManagerTest. testRemoteManagerConnectionRetryWithMultipleSenderTest
>>
>> RemoteManagerTest. testRemoteManagerConnectionRetryTest
>>
>>
>>
>> Both test cases have 9000 hard coded. If I kill all java process and
>> re-run them, they passed. But if I run them with other tests, they fail.
>> Looks like the port is taken by others.
>>
>>
>>
>> Looking further, we have several tests in other projects also use 9000.
>> I will go ahead to change them to some other ports. As they are just
>> tests, may not worth to randomly generate a port and retry.
>>
>>
>>
>> The product itself is good.
>>
>>
>>
>> ____________________
>>
>>
>>
>> Dec 04, 2014 9:37:52 AM
>> org.apache.reef.wake.remote.transport.netty.NettyMessagingTransport <init>
>>
>> SEVERE: Cannot bind to port 9000
>>
>> java.net.BindException: Address already in use: bind
>>
>> at sun.nio.ch.Net.bind0(Native Method)
>>
>> at sun.nio.ch.Net.bind(Net.java:444)
>>
>> at sun.nio.ch.Net.bind(Net.java:436)
>>
>> at
>> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
>>
>> at
>> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>>
>> at
>> io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
>>
>> at
>> io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:476)
>>
>> at
>> io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1021)
>>
>> at
>> io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:455)
>>
>> at
>> io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:440)
>>
>> at
>> io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:844)
>>
>> at
>> io.netty.channel.AbstractChannel.bind(AbstractChannel.java:195)
>>
>> at
>> io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:339)
>>
>> at
>> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:370)
>>
>> at
>> io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>>
>> at
>> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
>>
>> at java.lang.Thread.run(Thread.java:724)
>>
>>
>>
>>
>>
>> org.apache.reef.wake.remote.transport.exception.TransportRuntimeException:
>> Cannot bind to port 9000
>>
>> at
>> org.apache.reef.wake.remote.transport.netty.NettyMessagingTransport.<init>(NettyMessagingTransport.java:160)
>>
>> at
>> org.apache.reef.wake.remote.impl.DefaultRemoteManagerImplementation.<init>(DefaultRemoteManagerImplementation.java:83)
>>
>> at
>> org.apache.reef.wake.test.remote.RemoteManagerTest.getTestRemoteManager(RemoteManagerTest.java:285)
>>
>> at
>> org.apache.reef.wake.test.remote.RemoteManagerTest.testRemoteManagerConnectionRetryTest(RemoteManagerTest.java:107)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>>
>> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>>
>> 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.junit.runner.JUnitCore.run(JUnitCore.java:160)
>>
>> at
>> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
>>
>> at
>> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
>>
>> at
>> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at
>> com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
>>
>>
>>
>>
>>
>> Process finished with exit code -1
>>
>>
>>
>> -----Original Message-----
>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>> Sent: Thursday, December 04, 2014 5:20 AM
>> To: dev@reef.incubator.apache.org
>> Subject: Re: Test failures in WAKE
>>
>>
>>
>> Can you send me the logs of the failed test cases?
>>
>>
>>
>> ---
>>
>> Byung-Gon Chun
>>
>>
>>
>> Sent from my phone
>>
>>
>>
>> 2014. 12. 4. 오전 2:41 Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com<mailto:
>> Qiuhe.Wang@microsoft.com>> 작성:
>>
>>
>>
>> > That’s a good guess! I did try it from home last night. However, I
>> tried it again in the office this morning, get the same error.
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> > Results :
>>
>> >
>>
>> >
>>
>> >
>>
>> > Tests in error:
>>
>> >
>>
>> >
>> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285
>> ╗ TransportRuntime
>>
>> >
>>
>> >
>> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285
>> ╗ TransportRuntime
>>
>> >
>>
>> >
>>
>> >
>>
>> > Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>>
>> >
>>
>> >
>>
>> >
>>
>> > [INFO]
>> ------------------------------------------------------------------------
>>
>> >
>>
>> > [INFO] Reactor Summary:
>>
>> >
>>
>> > [INFO]
>>
>> >
>>
>> > [INFO] REEF Wake Project ................................. SUCCESS
>> [1.449s]
>>
>> >
>>
>> > [INFO] REEF Wake ......................................... FAILURE
>> [1:01.948s]
>>
>> >
>>
>> > [INFO]
>> ------------------------------------------------------------------------
>>
>> >
>>
>> > [INFO] BUILD FAILURE
>>
>> >
>>
>> > [INFO]
>> ------------------------------------------------------------------------
>>
>> >
>>
>> > [INFO] Total time: 1:03.579s
>>
>> >
>>
>> > [INFO] Finished at: Wed Dec 03 09:37:43 PST 2014
>>
>> >
>>
>> > [INFO] Final Memory: 19M/256M
>>
>> >
>>
>> > [INFO]
>> ------------------------------------------------------------------------
>>
>> >
>>
>> > [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
>> project wake: There are test failures.
>>
>> >
>>
>> > [ERROR]
>>
>> >
>>
>> > [ERROR] Please refer to
>> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports
>> for the individual test results.
>>
>> >
>>
>> > [ERROR] -> [Help 1]
>>
>> >
>>
>> > [ERROR]
>>
>> >
>>
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>>
>> >
>>
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>> >
>>
>> > [ERROR]
>>
>> >
>>
>> > [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>>
>> >
>>
>> > [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> >
>>
>> > [ERROR]
>>
>> >
>>
>> > [ERROR] After correcting the problems, you can resume the build with
>> the command
>>
>> >
>>
>> > [ERROR] mvn <goals> -rf :wake
>>
>> >
>>
>> > C:\Reef\ReefApache\incubator-reef\reef-wake [master]> git status
>>
>> >
>>
>> > On branch master
>>
>> >
>>
>> > Your branch is up-to-date with 'apache/master'.
>>
>> >
>>
>> >
>>
>> >
>>
>> > nothing to commit, working directory clean
>>
>> >
>>
>> >
>>
>> >
>>
>> > -----Original Message-----
>>
>> > From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>>
>> > Sent: Wednesday, December 03, 2014 3:10 AM
>>
>> > To: dev@reef.incubator.apache.org<ma...@reef.incubator.apache.org>
>>
>> > Subject: Re: Test failures in WAKE
>>
>> >
>>
>> >
>>
>> >
>>
>> > I ran tests at Mac and Linux successfully.
>>
>> >
>>
>> >
>>
>> >
>>
>> > Are you running the tests in your home network behind a DSL modem?
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> > On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE) <
>> Qiuhe.Wang@microsoft.com
>>
>> >
>>
>> >> wrote:
>>
>> >
>>
>> >
>>
>> >
>>
>> >> There are test failures when build/run test on WAKE. This is from
>>
>> >
>>
>> >> master branch. Do you have the same issue?
>>
>> >
>>
>> >
>>
>> >> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
>>
>> >
>>
>> >
>>
>> >> Results :
>>
>> >
>>
>> >
>>
>> >> Tests in error:
>>
>> >
>>
>> >
>>
>> >> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTe
>>
>> >
>>
>> >> st:132->getTestRemoteManager:285
>>
>> >
>>
>> >> ╗ TransportRuntime
>>
>> >
>>
>> >
>>
>> >> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRem
>>
>> >
>>
>> >> oteManager:285
>>
>> >
>>
>> >> ╗ TransportRuntime
>>
>> >
>>
>> >
>>
>> >> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>>
>> >
>>
>> >
>>
>> >> [INFO]
>>
>> >
>>
>> >> ----------------------------------------------------------------------
>>
>> >
>>
>> >> --
>>
>> >
>>
>> >> [INFO] Reactor Summary:
>>
>> >
>>
>> >> [INFO]
>>
>> >
>>
>> >> [INFO] REEF Wake Project ................................. SUCCESS
>>
>> >
>>
>> >> [1.063s] [INFO] REEF Wake .........................................
>>
>> >
>>
>> >> FAILURE [51.698s] [INFO]
>>
>> >
>>
>> >> ----------------------------------------------------------------------
>>
>> >
>>
>> >> --
>>
>> >
>>
>> >> [INFO] BUILD FAILURE
>>
>> >
>>
>> >> [INFO]
>>
>> >
>>
>> >> ----------------------------------------------------------------------
>>
>> >
>>
>> >> --
>>
>> >
>>
>> >> [INFO] Total time: 53.027s
>>
>> >
>>
>> >> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014 [INFO] Final Memory:
>>
>> >
>>
>> >> 16M/255M [INFO]
>>
>> >
>>
>> >> ----------------------------------------------------------------------
>>
>> >
>>
>> >> --
>>
>> >
>>
>> >> [ERROR] Failed to execute goal
>>
>> >
>>
>> >> org.apache.maven.plugins:maven-surefire-plugin:2.17:test
>>
>> >
>>
>> >> (default-test) on project wake: There are test failures.
>>
>> >
>>
>> >> [ERROR]
>>
>> >
>>
>> >> [ERROR] Please refer to
>>
>> >
>>
>> >> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-repor
>>
>> >
>>
>> >> ts
>>
>> >
>>
>> >> for the individual test results.
>>
>> >
>>
>> >> [ERROR] -> [Help 1]
>>
>> >
>>
>> >> [ERROR]
>>
>> >
>>
>> >> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>
>> >
>>
>> >> the -e switch.
>>
>> >
>>
>> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>> >
>>
>> >> [ERROR]
>>
>> >
>>
>> >> [ERROR] For more information about the errors and possible solutions,
>>
>> >
>>
>> >> please read the following articles:
>>
>> >
>>
>> >> [ERROR] [Help 1]
>>
>> >
>>
>> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> >
>>
>> >> [ERROR]
>>
>> >
>>
>> >> [ERROR] After correcting the problems, you can resume the build with
>>
>> >
>>
>> >> the command
>>
>> >
>>
>> >> [ERROR] mvn <goals> -rf :wake
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> >
>>
>> > --
>>
>> >
>>
>> > Byung-Gon Chun
>>
>
>
>
> --
> Byung-Gon Chun
>
--
Byung-Gon Chun
Re: Test failures in WAKE
Posted by Byung-Gon Chun <bg...@gmail.com>.
Thanks for letting me know. This is a minor problem. Nonetheless, it's good
to make Wake tests robust to port conflicts. I will file an issue.
On Fri, Dec 5, 2014 at 2:52 AM, Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com
> wrote:
> The two test failures are about port conflict on 9000.
>
>
>
> RemoteManagerTest. testRemoteManagerConnectionRetryWithMultipleSenderTest
>
> RemoteManagerTest. testRemoteManagerConnectionRetryTest
>
>
>
> Both test cases have 9000 hard coded. If I kill all java process and
> re-run them, they passed. But if I run them with other tests, they fail.
> Looks like the port is taken by others.
>
>
>
> Looking further, we have several tests in other projects also use 9000. I
> will go ahead to change them to some other ports. As they are just tests,
> may not worth to randomly generate a port and retry.
>
>
>
> The product itself is good.
>
>
>
> ____________________
>
>
>
> Dec 04, 2014 9:37:52 AM
> org.apache.reef.wake.remote.transport.netty.NettyMessagingTransport <init>
>
> SEVERE: Cannot bind to port 9000
>
> java.net.BindException: Address already in use: bind
>
> at sun.nio.ch.Net.bind0(Native Method)
>
> at sun.nio.ch.Net.bind(Net.java:444)
>
> at sun.nio.ch.Net.bind(Net.java:436)
>
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
>
> at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>
> at
> io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
>
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:476)
>
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1021)
>
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:455)
>
> at
> io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:440)
>
> at
> io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:844)
>
> at
> io.netty.channel.AbstractChannel.bind(AbstractChannel.java:195)
>
> at
> io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:339)
>
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:370)
>
> at
> io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
>
> at java.lang.Thread.run(Thread.java:724)
>
>
>
>
>
> org.apache.reef.wake.remote.transport.exception.TransportRuntimeException:
> Cannot bind to port 9000
>
> at
> org.apache.reef.wake.remote.transport.netty.NettyMessagingTransport.<init>(NettyMessagingTransport.java:160)
>
> at
> org.apache.reef.wake.remote.impl.DefaultRemoteManagerImplementation.<init>(DefaultRemoteManagerImplementation.java:83)
>
> at
> org.apache.reef.wake.test.remote.RemoteManagerTest.getTestRemoteManager(RemoteManagerTest.java:285)
>
> at
> org.apache.reef.wake.test.remote.RemoteManagerTest.testRemoteManagerConnectionRetryTest(RemoteManagerTest.java:107)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>
> 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.junit.runner.JUnitCore.run(JUnitCore.java:160)
>
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
>
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
>
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
>
>
>
>
>
> Process finished with exit code -1
>
>
>
> -----Original Message-----
> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> Sent: Thursday, December 04, 2014 5:20 AM
> To: dev@reef.incubator.apache.org
> Subject: Re: Test failures in WAKE
>
>
>
> Can you send me the logs of the failed test cases?
>
>
>
> ---
>
> Byung-Gon Chun
>
>
>
> Sent from my phone
>
>
>
> 2014. 12. 4. 오전 2:41 Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com<mailto:
> Qiuhe.Wang@microsoft.com>> 작성:
>
>
>
> > That’s a good guess! I did try it from home last night. However, I tried
> it again in the office this morning, get the same error.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Results :
>
> >
>
> >
>
> >
>
> > Tests in error:
>
> >
>
> >
> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285
> ╗ TransportRuntime
>
> >
>
> >
> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285
> ╗ TransportRuntime
>
> >
>
> >
>
> >
>
> > Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
> >
>
> >
>
> >
>
> > [INFO]
> ------------------------------------------------------------------------
>
> >
>
> > [INFO] Reactor Summary:
>
> >
>
> > [INFO]
>
> >
>
> > [INFO] REEF Wake Project ................................. SUCCESS
> [1.449s]
>
> >
>
> > [INFO] REEF Wake ......................................... FAILURE
> [1:01.948s]
>
> >
>
> > [INFO]
> ------------------------------------------------------------------------
>
> >
>
> > [INFO] BUILD FAILURE
>
> >
>
> > [INFO]
> ------------------------------------------------------------------------
>
> >
>
> > [INFO] Total time: 1:03.579s
>
> >
>
> > [INFO] Finished at: Wed Dec 03 09:37:43 PST 2014
>
> >
>
> > [INFO] Final Memory: 19M/256M
>
> >
>
> > [INFO]
> ------------------------------------------------------------------------
>
> >
>
> > [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
> project wake: There are test failures.
>
> >
>
> > [ERROR]
>
> >
>
> > [ERROR] Please refer to
> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports
> for the individual test results.
>
> >
>
> > [ERROR] -> [Help 1]
>
> >
>
> > [ERROR]
>
> >
>
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
>
> >
>
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> >
>
> > [ERROR]
>
> >
>
> > [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
>
> >
>
> > [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> >
>
> > [ERROR]
>
> >
>
> > [ERROR] After correcting the problems, you can resume the build with the
> command
>
> >
>
> > [ERROR] mvn <goals> -rf :wake
>
> >
>
> > C:\Reef\ReefApache\incubator-reef\reef-wake [master]> git status
>
> >
>
> > On branch master
>
> >
>
> > Your branch is up-to-date with 'apache/master'.
>
> >
>
> >
>
> >
>
> > nothing to commit, working directory clean
>
> >
>
> >
>
> >
>
> > -----Original Message-----
>
> > From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>
> > Sent: Wednesday, December 03, 2014 3:10 AM
>
> > To: dev@reef.incubator.apache.org<ma...@reef.incubator.apache.org>
>
> > Subject: Re: Test failures in WAKE
>
> >
>
> >
>
> >
>
> > I ran tests at Mac and Linux successfully.
>
> >
>
> >
>
> >
>
> > Are you running the tests in your home network behind a DSL modem?
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE) <
> Qiuhe.Wang@microsoft.com
>
> >
>
> >> wrote:
>
> >
>
> >
>
> >
>
> >> There are test failures when build/run test on WAKE. This is from
>
> >
>
> >> master branch. Do you have the same issue?
>
> >
>
> >
>
> >> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
>
> >
>
> >
>
> >> Results :
>
> >
>
> >
>
> >> Tests in error:
>
> >
>
> >
>
> >> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTe
>
> >
>
> >> st:132->getTestRemoteManager:285
>
> >
>
> >> ╗ TransportRuntime
>
> >
>
> >
>
> >> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRem
>
> >
>
> >> oteManager:285
>
> >
>
> >> ╗ TransportRuntime
>
> >
>
> >
>
> >> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
> >
>
> >
>
> >> [INFO]
>
> >
>
> >> ----------------------------------------------------------------------
>
> >
>
> >> --
>
> >
>
> >> [INFO] Reactor Summary:
>
> >
>
> >> [INFO]
>
> >
>
> >> [INFO] REEF Wake Project ................................. SUCCESS
>
> >
>
> >> [1.063s] [INFO] REEF Wake .........................................
>
> >
>
> >> FAILURE [51.698s] [INFO]
>
> >
>
> >> ----------------------------------------------------------------------
>
> >
>
> >> --
>
> >
>
> >> [INFO] BUILD FAILURE
>
> >
>
> >> [INFO]
>
> >
>
> >> ----------------------------------------------------------------------
>
> >
>
> >> --
>
> >
>
> >> [INFO] Total time: 53.027s
>
> >
>
> >> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014 [INFO] Final Memory:
>
> >
>
> >> 16M/255M [INFO]
>
> >
>
> >> ----------------------------------------------------------------------
>
> >
>
> >> --
>
> >
>
> >> [ERROR] Failed to execute goal
>
> >
>
> >> org.apache.maven.plugins:maven-surefire-plugin:2.17:test
>
> >
>
> >> (default-test) on project wake: There are test failures.
>
> >
>
> >> [ERROR]
>
> >
>
> >> [ERROR] Please refer to
>
> >
>
> >> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-repor
>
> >
>
> >> ts
>
> >
>
> >> for the individual test results.
>
> >
>
> >> [ERROR] -> [Help 1]
>
> >
>
> >> [ERROR]
>
> >
>
> >> [ERROR] To see the full stack trace of the errors, re-run Maven with
>
> >
>
> >> the -e switch.
>
> >
>
> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> >
>
> >> [ERROR]
>
> >
>
> >> [ERROR] For more information about the errors and possible solutions,
>
> >
>
> >> please read the following articles:
>
> >
>
> >> [ERROR] [Help 1]
>
> >
>
> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> >
>
> >> [ERROR]
>
> >
>
> >> [ERROR] After correcting the problems, you can resume the build with
>
> >
>
> >> the command
>
> >
>
> >> [ERROR] mvn <goals> -rf :wake
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > --
>
> >
>
> > Byung-Gon Chun
>
--
Byung-Gon Chun
RE: Test failures in WAKE
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
The two test failures are about port conflict on 9000.
RemoteManagerTest. testRemoteManagerConnectionRetryWithMultipleSenderTest
RemoteManagerTest. testRemoteManagerConnectionRetryTest
Both test cases have 9000 hard coded. If I kill all java process and re-run them, they passed. But if I run them with other tests, they fail. Looks like the port is taken by others.
Looking further, we have several tests in other projects also use 9000. I will go ahead to change them to some other ports. As they are just tests, may not worth to randomly generate a port and retry.
The product itself is good.
____________________
Dec 04, 2014 9:37:52 AM org.apache.reef.wake.remote.transport.netty.NettyMessagingTransport <init>
SEVERE: Cannot bind to port 9000
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:476)
at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1021)
at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:455)
at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:440)
at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:844)
at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:195)
at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:339)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:370)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:724)
org.apache.reef.wake.remote.transport.exception.TransportRuntimeException: Cannot bind to port 9000
at org.apache.reef.wake.remote.transport.netty.NettyMessagingTransport.<init>(NettyMessagingTransport.java:160)
at org.apache.reef.wake.remote.impl.DefaultRemoteManagerImplementation.<init>(DefaultRemoteManagerImplementation.java:83)
at org.apache.reef.wake.test.remote.RemoteManagerTest.getTestRemoteManager(RemoteManagerTest.java:285)
at org.apache.reef.wake.test.remote.RemoteManagerTest.testRemoteManagerConnectionRetryTest(RemoteManagerTest.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
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.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
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.junit.runner.JUnitCore.run(JUnitCore.java:160)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
Process finished with exit code -1
-----Original Message-----
From: Byung-Gon Chun [mailto:bgchun@gmail.com]
Sent: Thursday, December 04, 2014 5:20 AM
To: dev@reef.incubator.apache.org
Subject: Re: Test failures in WAKE
Can you send me the logs of the failed test cases?
---
Byung-Gon Chun
Sent from my phone
2014. 12. 4. 오전 2:41 Julia Wang (QIUHE) <Qi...@microsoft.com>> 작성:
> That’s a good guess! I did try it from home last night. However, I tried it again in the office this morning, get the same error.
>
>
>
>
>
> Results :
>
>
>
> Tests in error:
>
> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285 ╗ TransportRuntime
>
> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285 ╗ TransportRuntime
>
>
>
> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
>
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] REEF Wake Project ................................. SUCCESS [1.449s]
>
> [INFO] REEF Wake ......................................... FAILURE [1:01.948s]
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] Total time: 1:03.579s
>
> [INFO] Finished at: Wed Dec 03 09:37:43 PST 2014
>
> [INFO] Final Memory: 19M/256M
>
> [INFO] ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project wake: There are test failures.
>
> [ERROR]
>
> [ERROR] Please refer to C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports for the individual test results.
>
> [ERROR] -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the command
>
> [ERROR] mvn <goals> -rf :wake
>
> C:\Reef\ReefApache\incubator-reef\reef-wake [master]> git status
>
> On branch master
>
> Your branch is up-to-date with 'apache/master'.
>
>
>
> nothing to commit, working directory clean
>
>
>
> -----Original Message-----
> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> Sent: Wednesday, December 03, 2014 3:10 AM
> To: dev@reef.incubator.apache.org<ma...@reef.incubator.apache.org>
> Subject: Re: Test failures in WAKE
>
>
>
> I ran tests at Mac and Linux successfully.
>
>
>
> Are you running the tests in your home network behind a DSL modem?
>
>
>
>
>
> On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com
>
>> wrote:
>
>
>
>> There are test failures when build/run test on WAKE. This is from
>
>> master branch. Do you have the same issue?
>
>
>> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
>
>
>> Results :
>
>
>> Tests in error:
>
>
>> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTe
>
>> st:132->getTestRemoteManager:285
>
>> ╗ TransportRuntime
>
>
>> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRem
>
>> oteManager:285
>
>> ╗ TransportRuntime
>
>
>> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
>
>> [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [INFO] Reactor Summary:
>
>> [INFO]
>
>> [INFO] REEF Wake Project ................................. SUCCESS
>
>> [1.063s] [INFO] REEF Wake .........................................
>
>> FAILURE [51.698s] [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [INFO] BUILD FAILURE
>
>> [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [INFO] Total time: 53.027s
>
>> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014 [INFO] Final Memory:
>
>> 16M/255M [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [ERROR] Failed to execute goal
>
>> org.apache.maven.plugins:maven-surefire-plugin:2.17:test
>
>> (default-test) on project wake: There are test failures.
>
>> [ERROR]
>
>> [ERROR] Please refer to
>
>> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-repor
>
>> ts
>
>> for the individual test results.
>
>> [ERROR] -> [Help 1]
>
>> [ERROR]
>
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>
>> the -e switch.
>
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
>> [ERROR]
>
>> [ERROR] For more information about the errors and possible solutions,
>
>> please read the following articles:
>
>> [ERROR] [Help 1]
>
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>> [ERROR]
>
>> [ERROR] After correcting the problems, you can resume the build with
>
>> the command
>
>> [ERROR] mvn <goals> -rf :wake
>
>
>
>
>
>
>
>
> --
>
> Byung-Gon Chun
Re: Test failures in WAKE
Posted by Byung-Gon Chun <bg...@gmail.com>.
Can you send me the logs of the failed test cases?
---
Byung-Gon Chun
Sent from my phone
2014. 12. 4. 오전 2:41 Julia Wang (QIUHE) <Qi...@microsoft.com> 작성:
> That’s a good guess! I did try it from home last night. However, I tried it again in the office this morning, get the same error.
>
>
>
>
>
> Results :
>
>
>
> Tests in error:
>
> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285 ╗ TransportRuntime
>
> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285 ╗ TransportRuntime
>
>
>
> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
>
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
>
> [INFO]
>
> [INFO] REEF Wake Project ................................. SUCCESS [1.449s]
>
> [INFO] REEF Wake ......................................... FAILURE [1:01.948s]
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] BUILD FAILURE
>
> [INFO] ------------------------------------------------------------------------
>
> [INFO] Total time: 1:03.579s
>
> [INFO] Finished at: Wed Dec 03 09:37:43 PST 2014
>
> [INFO] Final Memory: 19M/256M
>
> [INFO] ------------------------------------------------------------------------
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project wake: There are test failures.
>
> [ERROR]
>
> [ERROR] Please refer to C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports for the individual test results.
>
> [ERROR] -> [Help 1]
>
> [ERROR]
>
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
>
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> [ERROR]
>
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
>
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> [ERROR]
>
> [ERROR] After correcting the problems, you can resume the build with the command
>
> [ERROR] mvn <goals> -rf :wake
>
> C:\Reef\ReefApache\incubator-reef\reef-wake [master]> git status
>
> On branch master
>
> Your branch is up-to-date with 'apache/master'.
>
>
>
> nothing to commit, working directory clean
>
>
>
> -----Original Message-----
> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> Sent: Wednesday, December 03, 2014 3:10 AM
> To: dev@reef.incubator.apache.org
> Subject: Re: Test failures in WAKE
>
>
>
> I ran tests at Mac and Linux successfully.
>
>
>
> Are you running the tests in your home network behind a DSL modem?
>
>
>
>
>
> On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com
>
>> wrote:
>
>
>
>> There are test failures when build/run test on WAKE. This is from
>
>> master branch. Do you have the same issue?
>
>
>> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
>
>
>> Results :
>
>
>> Tests in error:
>
>
>> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTe
>
>> st:132->getTestRemoteManager:285
>
>> ╗ TransportRuntime
>
>
>> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRem
>
>> oteManager:285
>
>> ╗ TransportRuntime
>
>
>> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
>
>> [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [INFO] Reactor Summary:
>
>> [INFO]
>
>> [INFO] REEF Wake Project ................................. SUCCESS
>
>> [1.063s] [INFO] REEF Wake .........................................
>
>> FAILURE [51.698s] [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [INFO] BUILD FAILURE
>
>> [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [INFO] Total time: 53.027s
>
>> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014 [INFO] Final Memory:
>
>> 16M/255M [INFO]
>
>> ----------------------------------------------------------------------
>
>> --
>
>> [ERROR] Failed to execute goal
>
>> org.apache.maven.plugins:maven-surefire-plugin:2.17:test
>
>> (default-test) on project wake: There are test failures.
>
>> [ERROR]
>
>> [ERROR] Please refer to
>
>> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-repor
>
>> ts
>
>> for the individual test results.
>
>> [ERROR] -> [Help 1]
>
>> [ERROR]
>
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>
>> the -e switch.
>
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
>> [ERROR]
>
>> [ERROR] For more information about the errors and possible solutions,
>
>> please read the following articles:
>
>> [ERROR] [Help 1]
>
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>> [ERROR]
>
>> [ERROR] After correcting the problems, you can resume the build with
>
>> the command
>
>> [ERROR] mvn <goals> -rf :wake
>
>
>
>
>
>
>
>
> --
>
> Byung-Gon Chun
RE: Test failures in WAKE
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com>.
That’s a good guess! I did try it from home last night. However, I tried it again in the office this morning, get the same error.
Results :
Tests in error:
RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285 ╗ TransportRuntime
RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285 ╗ TransportRuntime
Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] REEF Wake Project ................................. SUCCESS [1.449s]
[INFO] REEF Wake ......................................... FAILURE [1:01.948s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:03.579s
[INFO] Finished at: Wed Dec 03 09:37:43 PST 2014
[INFO] Final Memory: 19M/256M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project wake: There are test failures.
[ERROR]
[ERROR] Please refer to C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :wake
C:\Reef\ReefApache\incubator-reef\reef-wake [master]> git status
On branch master
Your branch is up-to-date with 'apache/master'.
nothing to commit, working directory clean
-----Original Message-----
From: Byung-Gon Chun [mailto:bgchun@gmail.com]
Sent: Wednesday, December 03, 2014 3:10 AM
To: dev@reef.incubator.apache.org
Subject: Re: Test failures in WAKE
I ran tests at Mac and Linux successfully.
Are you running the tests in your home network behind a DSL modem?
On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com
> wrote:
> There are test failures when build/run test on WAKE. This is from
> master branch. Do you have the same issue?
>
> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
>
> Results :
>
> Tests in error:
>
> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTe
> st:132->getTestRemoteManager:285
> ╗ TransportRuntime
>
> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRem
> oteManager:285
> ╗ TransportRuntime
>
> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Reactor Summary:
> [INFO]
> [INFO] REEF Wake Project ................................. SUCCESS
> [1.063s] [INFO] REEF Wake .........................................
> FAILURE [51.698s] [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 53.027s
> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014 [INFO] Final Memory:
> 16M/255M [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.17:test
> (default-test) on project wake: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-repor
> ts
> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with
> the command
> [ERROR] mvn <goals> -rf :wake
>
--
Byung-Gon Chun
Re: Test failures in WAKE
Posted by Byung-Gon Chun <bg...@gmail.com>.
I ran tests at Mac and Linux successfully.
Are you running the tests in your home network behind a DSL modem?
On Wed, Dec 3, 2014 at 4:54 PM, Julia Wang (QIUHE) <Qiuhe.Wang@microsoft.com
> wrote:
> There are test failures when build/run test on WAKE. This is from master
> branch. Do you have the same issue?
>
> C:\Reef\ReefApache\incubator-reef\reef-wake [master]>mvn clean install
>
> Results :
>
> Tests in error:
>
> RemoteManagerTest.testRemoteManagerConnectionRetryWithMultipleSenderTest:132->getTestRemoteManager:285
> ╗ TransportRuntime
>
> RemoteManagerTest.testRemoteManagerConnectionRetryTest:107->getTestRemoteManager:285
> ╗ TransportRuntime
>
> Tests run: 66, Failures: 0, Errors: 2, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] REEF Wake Project ................................. SUCCESS [1.063s]
> [INFO] REEF Wake ......................................... FAILURE
> [51.698s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 53.027s
> [INFO] Finished at: Tue Dec 02 23:50:28 PST 2014
> [INFO] Final Memory: 16M/255M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
> project wake: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> C:\Reef\ReefApache\incubator-reef\reef-wake\wake\target\surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :wake
>
--
Byung-Gon Chun