Hm, interesting, it just failed for me on my Mac. Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 183.017 sec <<< FAILURE! - in org.apache.brooklyn.core.dsl.external.ExternalConfigBrooklynPropertiesOsgiTest testOSGIWithPrefix(org.apache.brooklyn.core.dsl.external.ExternalConfigBrooklynPropertiesOsgiTest) Time elapsed: 183.016 sec <<< ERROR! java.rmi.NotBoundException: 0db5af64-ab19-4efe-a4f3-a6b41d3f583c at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:227) at sun.rmi.registry.RegistryImpl_Skel.dispatch(RegistryImpl_Skel.java:115) at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:468) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:300) at sun.rmi.transport.Transport$1.run(Transport.java:200) at sun.rmi.transport.Transport$1.run(Transport.java:197) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:196) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:375) at sun.rmi.registry.RegistryImpl_Stub.lookup(RegistryImpl_Stub.java:119) at org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl.getRemoteBundleContext(RemoteBundleContextClientImpl.java:248) at org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl.waitForState(RemoteBundleContextClientImpl.java:218) at org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer.waitForState(KarafTestContainer.java:659) at org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer.startKaraf(KarafTestContainer.java:262) at org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer.start(KarafTestContainer.java:194) at org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:79) at org.ops4j.pax.exam.junit.impl.ProbeRunner$2.evaluate(ProbeRunner.java:267) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.ops4j.pax.exam.junit.impl.ProbeRunner.run(ProbeRunner.java:98) at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:93) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:108) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:78) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:144) 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: ExternalConfigBrooklynPropertiesOsgiTest.testOSGIWithPrefix » NotBound 0db5af6... Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 ± java -version java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) ± uname -a Darwin My-MacBook-Pro.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64 Will have a quick look into it but it's been a while since I've done anything with Pax On Fri, 24 Jan 2020 at 17:35, Aled Sage <[email protected]> wrote: > Thanks Martin, > > Which environment(s) is it passing and failing in? > > If this works in our apache jenkins and for contributors locally, and > especially if the environment it fails in is "niche" then a +1 from me > for skipping the test so we can get the release candidate built. > > Aled > > p.s. the test passes for me locally on my mac - I tested it with: > > mvn test > > -Dtest=org.apache.brooklyn.core.dsl.external.ExternalConfigBrooklynPropertiesOsgiTest > > > On 24/01/2020 16:35, Martin Harris wrote: > > Hi Folks, > > > > In building the first release candidate for Brooklyn 1.0.0, we've hit > > an issue when trying to run the build. The > > `org.apache.brooklyn.AssemblyTest` and > > > `org.apache.brooklyn.core.dsl.external.ExternalConfigBrooklynPropertiesOsgiTest` > > > tests are failing in certain environments, but are not reproducible in > > other environments > > > > So far, we have been unable to determine the specific cause, and have > > not been able to find a resolution > > > > The exact failures and relevant section of the log are attached > > > > As the issue seem environment specific, and no other issues have been > > identified in the built artifacts, we are considering simply disabling > > the tests > > > > If you think we should not disable the tests, or if you can provide > > any feedback on the cause of the issue, please let us know. Otherwise, > > we will disable the tests and continue with the build early next week. > > A lazy consensus applies > > > > Thanks > > > > -- > > Martin Harris > > Lead Software Engineer > > > > *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud > > > > E: [email protected] <mailto:[email protected]> > > M: 07989 047855 > > > > Need a hand with AWS? Get a Free Consultation. > > <https://go.cloudsoft.io/healthcheck/> >
