Last patch merged to openflowplugin stable/oxygen branch was on October
4th, so no recent change. It looks like test is trying to start a client to
test the tls connection and timed out. I never seen this test failing
before. I will wait for tomorrow's autorelease and see if this happens
again. If it happens again, we will investigate the issue.

Thanks
Anil

On Tue, Oct 16, 2018 at 10:41 PM Ariel Adam <aa...@redhat.com> wrote:

> Anil, did you guys change anything?
> We get the following timeout exception:
>
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.opendaylight.openflowjava.protocol.it.integration.IntegrationTest
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 32.949 sec 
> <<< FAILURE! - in 
> org.opendaylight.openflowjava.protocol.it.integration.IntegrationTest
> testTlsHandshake(org.opendaylight.openflowjava.protocol.it.integration.IntegrationTest)
>   Time elapsed: 3.793 sec  <<< ERROR!
> java.util.concurrent.TimeoutException: Waited 2000 milliseconds for 
> com.google.common.util.concurrent.SettableFuture@242ff747[status=PENDING]
>       at 
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:470)
>       at 
> com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:92)
>       at 
> org.opendaylight.openflowjava.protocol.it.integration.IntegrationTest.createAndStartClient(IntegrationTest.java:255)
>       at 
> org.opendaylight.openflowjava.protocol.it.integration.IntegrationTest.testTlsHandshake(IntegrationTest.java:134)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:498)
>       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.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:283)
>       at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>       at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>       at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>       at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>       at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>       at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
>
>
> Results :
>
> Tests in error:
>   IntegrationTest.testTlsHandshake:134->createAndStartClient:255 » Timeout 
> Waite...
>
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0
>
>
> Thanks.
>
> On Wed, Oct 17, 2018 at 6:57 AM Jenkins <
> jenkins-dontre...@opendaylight.org> wrote:
>
>> Attention openflowplugin-devs,
>>
>> Autorelease oxygen failed to build openflow-protocol-it from
>> openflowplugin in build
>> 455. Attached is a snippet of the error message related to the
>> failure that we were able to automatically parse as well as console logs.
>>
>>
>> Console Logs:
>>
>> https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-oxygen/455
>>
>> Jenkins Build:
>>
>> https://jenkins.opendaylight.org/releng/job/autorelease-release-oxygen/455/
>>
>> Please review and provide an ETA on when a fix will be available.
>>
>> Thanks,
>> ODL releng/autorelease team
>>
>> _______________________________________________
>> release mailing list
>> rele...@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/release
>>
>

-- 
Thanks
Anil
_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to