Re: Master build broken

2016-02-22 Thread Sam Corbett
There are several unreliable tests at the moment. Some have been noted 
in JIRA:


AssemblyTest.checkBrooklynCoreFeature 
(https://issues.apache.org/jira/browse/BROOKLYN-216)
AbstractControllerTest.testUpdateCalledWhenChildHostnameAndPortChanges 
(https://issues.apache.org/jira/browse/BROOKLYN-206)
ControlledDynamicWebAppClusterTest.testTheTestJavaWebApp 
(https://issues.apache.org/jira/browse/BROOKLYN-203)
HotStandbyTest.testChangeMode 
(https://issues.apache.org/jira/browse/BROOKLYN-204)
CassandraDatacenterTest.testPopulatesInitialSeeds 
(https://issues.apache.org/jira/browse/BROOKLYN-205)


And other recent failures from Jenkins:

RebindCatalogItemTest.testAddAndRebindAndDeleteLocation 
(https://builds.apache.org/job/brooklyn-master-build/19/console)
SecureKeysAndSignerTest.testInjectCertificateAuthority 
(https://builds.apache.org/job/brooklyn-master-build/15/console)
BasicStartableTest.testTransitionsThroughLifecycles 
(https://builds.apache.org/job/brooklyn-master-build/16/console)


I've had a small amount of luck reproducing some of these by using a VM 
with a single CPU.


Sam

On 20/02/2016 11:23, Aled Sage wrote:

Thanks for pointing this out Robert.

TL;DR: does anyone working on OSGi recently have bandwidth to look at 
this please?


---
The failing test is 
org.apache.brooklyn.AssemblyTest.checkBrooklynCoreFeature (in 
brooklyn-itest).


---
Perhaps unrelated, this test also failed non-deterministically with a 
different (?) error, e.g. in 
https://github.com/apache/brooklyn-server/pull/29:


   Exception in thread "JMX Connector Thread
[service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-brooklyn]"
   java.lang.RuntimeException:
   Port already in use: 4;
   You may have started two containers.  If you need to start a second
   container or the default ports are already in use update the config
   file etc/org.apache.karaf.management.cfg and change the Registry
   Port and Server Port to unused ports
at
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:268)

I put that one down to concurrent processes on the same test box, 
where we need to configure it to use a random available port rather 
than a specific port number.


---
The test passes locally, but interestingly I see the same "Unknown 
protocol: mvn" in my stdout.


---
The error in the apache build is:

   org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up
   waiting for service org.apache.karaf.features.BootFinished

Stdout includes:

org.apache.karaf.features.core[org.apache.karaf.features.internal.service.BootFeaturesInstaller]
   : Error installing boot features
   org.apache.karaf.features.internal.util.MultiException: Error
   restarting bundles
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:844)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Suppressed: org.osgi.framework.BundleException: Activator start
   error in bundle org.apache.felix.metatype [73].
at
org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)
at
   org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
at
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
at
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1189)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:836)
... 6 more
Caused by: java.lang.IllegalStateException: Unknown protocol: mvn
at
org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:482)
at
org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:474)
at java.net.URL.toExternalForm(URL.java:921)
at java.net.URL.toString(URL.java:907)
at
java.lang.ClassLoader.defineClassSourceLocation(ClassLoader.java:676)
at java.lang.ClassLoader.defineClass(ClassLoader.java:797)
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2370)
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2154)
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1542)
at

Re: Master build broken

2016-02-20 Thread Aled Sage

Thanks for pointing this out Robert.

TL;DR: does anyone working on OSGi recently have bandwidth to look at 
this please?


---
The failing test is 
org.apache.brooklyn.AssemblyTest.checkBrooklynCoreFeature (in 
brooklyn-itest).


---
Perhaps unrelated, this test also failed non-deterministically with a 
different (?) error, e.g. in 
https://github.com/apache/brooklyn-server/pull/29:


   Exception in thread "JMX Connector Thread
   [service:jmx:rmi://0.0.0.0:4/jndi/rmi://0.0.0.0:1099/karaf-brooklyn]"
   java.lang.RuntimeException:
   Port already in use: 4;
   You may have started two containers.  If you need to start a second
   container or the default ports are already in use update the config
   file etc/org.apache.karaf.management.cfg and change the Registry
   Port and Server Port to unused ports
at
   
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:268)

I put that one down to concurrent processes on the same test box, where 
we need to configure it to use a random available port rather than a 
specific port number.


---
The test passes locally, but interestingly I see the same "Unknown 
protocol: mvn" in my stdout.


---
The error in the apache build is:

   org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up
   waiting for service org.apache.karaf.features.BootFinished

Stdout includes:

   
org.apache.karaf.features.core[org.apache.karaf.features.internal.service.BootFeaturesInstaller]
   : Error installing boot features
   org.apache.karaf.features.internal.util.MultiException: Error
   restarting bundles
at
   org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:844)
at
   
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)
at
   
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
   
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
   
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Suppressed: org.osgi.framework.BundleException: Activator start
   error in bundle org.apache.felix.metatype [73].
at
   org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)
at
   org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
at
   org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
at
   org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
at
   
org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1189)
at
   org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:836)
... 6 more
Caused by: java.lang.IllegalStateException: Unknown protocol: mvn
at
   
org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:482)
at
   
org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:474)
at java.net.URL.toExternalForm(URL.java:921)
at java.net.URL.toString(URL.java:907)
at
   java.lang.ClassLoader.defineClassSourceLocation(ClassLoader.java:676)
at java.lang.ClassLoader.defineClass(ClassLoader.java:797)
at
   
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2370)
at
   
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2154)
at
   
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1542)
at
   
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)
at
   
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
   
org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(BundleWiringImpl.java:1415)
at
   org.apache.felix.framework.Felix.createBundleActivator(Felix.java:4468)
at
   org.apache.felix.framework.Felix.activateBundle(Felix.java:2221)
... 11 more
Suppressed: org.osgi.framework.BundleException: Activator start
   error in bundle org.apache.karaf.services.eventadmin [100].
at
   org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)
at
   org.apache.felix.framework.Felix.startBundle(Felix.java:2144)
at
   org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
at
   org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
at
   

Master build broken

2016-02-19 Thread Robert Moss
Hi All,

It appears the brooklyn-master-build is failing[1].  This means that no
snapshots have been published to the maven since 10th Feb.  Would anyone be
will to help me resolve this, as there are commits which have been commited
recently which we'd like to make use of in our downstream brooklyn-tosca
project?

Robert

[1] https://builds.apache.org/job/brooklyn-master-build/