Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
8313
Description
https://lists.opendaylight.org/pipermail/release/2017-April/010380.html
After putting some serious effort into trying to fix this, I am unable to
figure out why it is failing in the first place:
20:34:17 -------------------------------------------------------
20:34:17 T E S T S
20:34:17 -------------------------------------------------------
20:34:22 Running org.opendaylight.odlparent.featuretest.SingleFeatureTest
20:37:41 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time
elapsed: 198.433 sec <<< FAILURE! - in
org.opendaylight.odlparent.featuretest.SingleFeatureTest
20:37:41 installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl:
file:/w/workspace/aaa-verify-carbon-mvn33-openjdk8/features/authn/features4-aaa/target/feature/feature.xml,
Feature: odl-aaa-encryption-service 0.5.0.SNAPSHOT] Time elapsed:
25.312 sec <<< FAILURE!
20:37:41 java.lang.AssertionError: diag: Stopping
20:37:41 1. NOK org.opendaylight.aaa.encrypt-service: OSGi state =
Active, Karaf bundleState = Stopping
20:37:41 at org.opendaylight.odlparent.bundles4test.TestBundleDiag.checkBundleDiagInfos(TestBundleDiag.java:86)
20:37:41 at org.opendaylight.odlparent.bundles4test.TestBundleDiag.checkBundleDiagInfos(TestBundleDiag.java:50)
20:37:41 at org.opendaylight.odlparent.featuretest.SingleFeatureTest.installFeature(SingleFeatureTest.java:387)
20:37:41 at org.opendaylight.odlparent.featuretest.SingleFeatureTest.installFeatureCatchAndLog(SingleFeatureTest.java:338)
20:37:41 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
20:37:41 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
20:37:41 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
20:37:41 at java.lang.reflect.Method.invoke(Method.java:498)
20:37:41 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
20:37:41 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
20:37:41 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
20:37:41 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
20:37:41 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
20:37:41 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
20:37:41 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
20:37:41 at java.lang.Thread.run(Thread.java:745)
20:37:41
Anyone have any ideas? This comes from this patch [0]'s verify job,
but doesn't appear to be caused by the patch at hand. In fact, I am
not even sure why this test started randomly failing. Any help is
appreciated.
Thanks,
Ryan Goulding
Attachments
Issue Links
- blocks
-
INTDIST-68 distribution-check is not stable in Nitrogen
- Resolved