https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/ODLPARENT-88 odlparent <p>A good examples of this bug would be <span class="error">&#91;1&#93;</span>,<span class="error">&#91;2&#93;</span>. Basicly singleFeatureTest somethimes failes just with - Build timed out (after 360 minutes). Marking the build as failed - which is timeout for whole build. Maximum time for one feature should be 10 minutes, But in those two examples you can see that time exceeds this 10 mins by far more. </p> <p><span class="error">&#91;1&#93;</span> <a href="https://jenkins.opendaylight.org/releng/job/netconf-verify-carbon-mvn33-openjdk8/1685/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/netconf-verify-carbon-mvn33-openjdk8/1685/console</a><br/> <span class="error">&#91;2&#93;</span> <a href="https://jenkins.opendaylight.org/releng/job/netconf-verify-carbon-mvn33-openjdk8/1678/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/netconf-verify-carbon-mvn33-openjdk8/1678/console</a></p> <p>Operating System: All<br/> Platform: All</p> ODLPARENT-88

Testing of one karaf4 feature may take more than 10 minutes

Bug Resolved Cannot Reproduce Unassigned Miroslav Kovac Fri, 28 Apr 2017 11:01:05 +0000 Mon, 6 Sep 2021 09:33:33 +0000 Mon, 6 Sep 2021 09:33:33 +0000 2.0.5 General 0 2 <p><a href="https://logs.opendaylight.org/releng/jenkins092/netconf-verify-carbon-mvn33-openjdk8/1685/archives/features/netconf-connector/odl-netconf-connector-all/target/surefire-reports/org.opendaylight.odlparent.featuretest.SingleFeatureTest-output.txt.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netconf-verify-carbon-mvn33-openjdk8/1685/archives/features/netconf-connector/odl-netconf-connector-all/target/surefire-reports/org.opendaylight.odlparent.featuretest.SingleFeatureTest-output.txt.gz</a></p> <p>This looks like the test itself failed in ~10 minutes:</p> <p>2017-04-28 08:23:59,907 | ERROR | ime-limited test | SingleFeatureTest | 73 - PAXEXAM-PROBE-5faad4d3-3ec4-47f8-b247-0e475d126ba5 - 0.0.0 | installFeature() failed<br/> java.lang.InterruptedException<br/> at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:404)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.FutureTask.get(FutureTask.java:191)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvisionInThread(FeaturesServiceImpl.java:1077)<span class="error">&#91;8:org.apache.karaf.features.core:4.0.9&#93;</span><br/> at org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:954)<span class="error">&#91;8:org.apache.karaf.features.core:4.0.9&#93;</span><br/> at org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:847)<span class="error">&#91;8:org.apache.karaf.features.core:4.0.9&#93;</span><br/> at org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:832)<span class="error">&#91;8:org.apache.karaf.features.core:4.0.9&#93;</span><br/> at org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:837)<span class="error">&#91;8:org.apache.karaf.features.core:4.0.9&#93;</span><br/> at org.opendaylight.odlparent.featuretest.SingleFeatureTest.installFeature(SingleFeatureTest.java:368)<br/> at org.opendaylight.odlparent.featuretest.SingleFeatureTest.installFeatureCatchAndLog(SingleFeatureTest.java:338)<br/> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.lang.reflect.Method.invoke(Method.java:498)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)<span class="error">&#91;71:org.ops4j.pax.tipi.junit:4.12.0.1&#93;</span><br/> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)<span class="error">&#91;71:org.ops4j.pax.tipi.junit:4.12.0.1&#93;</span><br/> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)<span class="error">&#91;71:org.ops4j.pax.tipi.junit:4.12.0.1&#93;</span><br/> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)<span class="error">&#91;71:org.ops4j.pax.tipi.junit:4.12.0.1&#93;</span><br/> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)<span class="error">&#91;71:org.ops4j.pax.tipi.junit:4.12.0.1&#93;</span><br/> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)<span class="error">&#91;71:org.ops4j.pax.tipi.junit:4.12.0.1&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:266)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.8.0_121&#93;</span></p> <p>after which the container started stopping, but it seems the shutdown process hung on:</p> <p>2017-04-28 08:24:01,019 | INFO | Framework stop | Activator | 330 - org.ops4j.pax.web.pax-web-extender-war - 4.3.0 | Destroying extension for bundle org.opendaylight.aaa.idmlight</p> <p>On odlparent side, we probably should instruct pax-exam to hard-kill the container after a installFeature() timeout.</p> <p>Furthermore we should dump the bundle status to identify who is holding up the startup.</p> <p>&gt; On odlparent side, we probably should instruct pax-exam to<br/> &gt; hard-kill the container after a installFeature() timeout.</p> <p>Hm, is there a ready-made option for this? I don't recall seeing one..</p> <p>This may be more than 3' of work and require contributing to PAX?</p> <p>&gt; Furthermore we should dump the bundle status to<br/> &gt; identify who is holding up the startup.</p> <p>Following <a href="https://git.opendaylight.org/gerrit/#/c/51908/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/51908/</a>, normally this should already happen? It won't dump the status just when it times out, but normally should have just before? (Using Awaitility, I'm not sure we can do the dump just before the timeout; we may have to make a contribution to Awaitility <span class="error">&#91;or justwrite the spin loop ourselves&#93;</span>; or perhaps we can catch InterruptedException and dump there. But having it just a little earlier in the log as is already may be sufficient?)</p> <p>Most SFTs finish in under a minute. There really is not much we can do on testing side to speed things up.</p> Duplicate ODLPARENT-89 Development External issue ID 8333 External issue URL Issue Type Rank 0|i0238f: