You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2012/10/28 00:07:32 UTC

Builds on Jenkins

At present, many of our builds at Jenkins fail [0] and it looks like they
are not stable. Some of the build are failing since three or more weeks.
This is really bad.
Let's reserve some time to fix this and bring the Camel builds back to
stable. Assign one of the issues to yourself and work on it.

[0] https://builds.apache.org/view/A-F/view/Camel/
[1] https://issues.apache.org/jira/browse/CAMEL-5749
[2] https://issues.apache.org/jira/browse/CAMEL-5750
[3] https://issues.apache.org/jira/browse/CAMEL-5751
[4] https://issues.apache.org/jira/browse/CAMEL-5752
[5] https://issues.apache.org/jira/browse/CAMEL-5753

Thanks in advance,
Christian

--

Re: Builds on Jenkins

Posted by Scott England-Sullivan <su...@gmail.com>.
Claus,

Regarding the manifest, as a work around, I do the following to
compare manifest files:

Generate the original MANIFEST.MF using mvn bundle:manifest
Open the manifests with Eclipse using the manifest editor
Click the source tab
Ctrl-Shift F(Win)
Cmd-Shift F (Mac)
Then Compare

In eclipse you can also Cmd Click the two files and then in the mouse
context select Compare --> Each Other.

Kludgy but it works.

Best Regards,
Scott ES


On Mon, Oct 29, 2012 at 12:05 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay I reverted back to OSGi 4.2 which works.
>
> So OSGi 4.3 is *not* backwards compatible which is a real PITA.
> So we would need to compile camel-core-osgi / camel-spring /
> camel-blueprint et all with OSGi 4.2.
> And then have our fingers crossed that these runs on an OSGi 4.3 runtime?
>
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> (default-compile) on project camel-core: Compilation failure:
> Compilation failure:
> [ERROR] /Users/davsclaus/workspace/camel/camel-core/src/main/java/org/apache/camel/impl/osgi/Activator.java:[437,43]
> cannot find symbol
> [ERROR] symbol  : method
> registerService(java.lang.String,org.apache.camel.impl.osgi.Activator.BaseService,java.util.Dictionary<capture#903
> of ?,capture#530 of ?>)
> [ERROR] location: interface org.osgi.framework.BundleContext
> [ERROR] /Users/davsclaus/workspace/camel/camel-core/src/main/java/org/apache/camel/impl/osgi/Activator.java:[399,48]
> incompatible types
> [ERROR] found   : java.lang.Class<capture#0 of ?>
> [ERROR] required: java.lang.Class<T>
> [ERROR] -> [Help 1]
>
>
> On Mon, Oct 29, 2012 at 3:29 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> Okay it took me a long time to dig into this. I kinda hate the
>> computer generated MANIFEST.MF files in those 76 cut lines format.
>> Makes comparing 2 version a big challenge. If at at least the BND tool
>> could generat a line per package, making diff much easier for humans.
>>
>> Only by using a visual diff tool I could spot a problem.
>>
>> In Camel 2.10 the MANIFEST.MF is generated with [1.2,2) for the
>> spring-dm osgi stuff.
>>
>> sembler;version="[3,4)",org.springframework.jmx.export.metadata;version
>>  ="[3,4)",org.springframework.osgi.context;version="[1.2,2)";resolution:
>>  =optional,org.springframework.remoting.support;version="[3,4)",org.spri
>>  ngframework.transaction;version="[3,4)",org.springframework.transaction
>>  .support;version="[3,4)",org.springframework.util;version="[3,4)",org.w
>>  3c.dom
>>
>>
>> But on trunk its using spring framework range [3,4) which is wrong
>>
>> sembler;version="[3,4)",org.springframework.jmx.export.metadata;version
>>  ="[3,4)",org.springframework.osgi.context;version="[3,4)";resolution:=o
>>  ptional,org.springframework.remoting.support;version="[3,4)",org.spring
>>  framework.transaction;version="[3,4)",org.springframework.transaction.s
>>  upport;version="[3,4)",org.springframework.util;version="[3,4)",org.w3c
>>  .dom
>>
>>
>> So I would need to figure out in our marvelous build system, to make
>> it use the old behavior, so it can use the correct version ranges.
>>
>>
>>
>>
>>
>> On Mon, Oct 29, 2012 at 10:57 AM, Babak Vahdat
>> <ba...@swissonline.ch> wrote:
>>> Hi
>>>
>>> If I remember correctly, yesterday that was also one of my suspections as
>>> well so that I reverted locally back to 4.2, however still observing the
>>> same behaviour.
>>> Also tried downgrading felix-compendium, felix-configadmin and
>>> felix-framework versions back to what they were before the upgrade to OSGi
>>> 4.3 and still no change in the behaviour.
>>>
>>> I suspect the OSGi POM settings being broken *before* this OSGi upgrade,
>>> like <camel.osgi.import.defaults> and whatnot.
>>>
>>> Babak
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://camel.465427.n5.nabble.com/Builds-on-Jenkins-tp5721653p5721717.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen

Re: Builds on Jenkins

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Okay I reverted back to OSGi 4.2 which works.

So OSGi 4.3 is *not* backwards compatible which is a real PITA.
So we would need to compile camel-core-osgi / camel-spring /
camel-blueprint et all with OSGi 4.2.
And then have our fingers crossed that these runs on an OSGi 4.3 runtime?


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
(default-compile) on project camel-core: Compilation failure:
Compilation failure:
[ERROR] /Users/davsclaus/workspace/camel/camel-core/src/main/java/org/apache/camel/impl/osgi/Activator.java:[437,43]
cannot find symbol
[ERROR] symbol  : method
registerService(java.lang.String,org.apache.camel.impl.osgi.Activator.BaseService,java.util.Dictionary<capture#903
of ?,capture#530 of ?>)
[ERROR] location: interface org.osgi.framework.BundleContext
[ERROR] /Users/davsclaus/workspace/camel/camel-core/src/main/java/org/apache/camel/impl/osgi/Activator.java:[399,48]
incompatible types
[ERROR] found   : java.lang.Class<capture#0 of ?>
[ERROR] required: java.lang.Class<T>
[ERROR] -> [Help 1]


On Mon, Oct 29, 2012 at 3:29 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay it took me a long time to dig into this. I kinda hate the
> computer generated MANIFEST.MF files in those 76 cut lines format.
> Makes comparing 2 version a big challenge. If at at least the BND tool
> could generat a line per package, making diff much easier for humans.
>
> Only by using a visual diff tool I could spot a problem.
>
> In Camel 2.10 the MANIFEST.MF is generated with [1.2,2) for the
> spring-dm osgi stuff.
>
> sembler;version="[3,4)",org.springframework.jmx.export.metadata;version
>  ="[3,4)",org.springframework.osgi.context;version="[1.2,2)";resolution:
>  =optional,org.springframework.remoting.support;version="[3,4)",org.spri
>  ngframework.transaction;version="[3,4)",org.springframework.transaction
>  .support;version="[3,4)",org.springframework.util;version="[3,4)",org.w
>  3c.dom
>
>
> But on trunk its using spring framework range [3,4) which is wrong
>
> sembler;version="[3,4)",org.springframework.jmx.export.metadata;version
>  ="[3,4)",org.springframework.osgi.context;version="[3,4)";resolution:=o
>  ptional,org.springframework.remoting.support;version="[3,4)",org.spring
>  framework.transaction;version="[3,4)",org.springframework.transaction.s
>  upport;version="[3,4)",org.springframework.util;version="[3,4)",org.w3c
>  .dom
>
>
> So I would need to figure out in our marvelous build system, to make
> it use the old behavior, so it can use the correct version ranges.
>
>
>
>
>
> On Mon, Oct 29, 2012 at 10:57 AM, Babak Vahdat
> <ba...@swissonline.ch> wrote:
>> Hi
>>
>> If I remember correctly, yesterday that was also one of my suspections as
>> well so that I reverted locally back to 4.2, however still observing the
>> same behaviour.
>> Also tried downgrading felix-compendium, felix-configadmin and
>> felix-framework versions back to what they were before the upgrade to OSGi
>> 4.3 and still no change in the behaviour.
>>
>> I suspect the OSGi POM settings being broken *before* this OSGi upgrade,
>> like <camel.osgi.import.defaults> and whatnot.
>>
>> Babak
>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/Builds-on-Jenkins-tp5721653p5721717.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Builds on Jenkins

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Okay it took me a long time to dig into this. I kinda hate the
computer generated MANIFEST.MF files in those 76 cut lines format.
Makes comparing 2 version a big challenge. If at at least the BND tool
could generat a line per package, making diff much easier for humans.

Only by using a visual diff tool I could spot a problem.

In Camel 2.10 the MANIFEST.MF is generated with [1.2,2) for the
spring-dm osgi stuff.

sembler;version="[3,4)",org.springframework.jmx.export.metadata;version
 ="[3,4)",org.springframework.osgi.context;version="[1.2,2)";resolution:
 =optional,org.springframework.remoting.support;version="[3,4)",org.spri
 ngframework.transaction;version="[3,4)",org.springframework.transaction
 .support;version="[3,4)",org.springframework.util;version="[3,4)",org.w
 3c.dom


But on trunk its using spring framework range [3,4) which is wrong

sembler;version="[3,4)",org.springframework.jmx.export.metadata;version
 ="[3,4)",org.springframework.osgi.context;version="[3,4)";resolution:=o
 ptional,org.springframework.remoting.support;version="[3,4)",org.spring
 framework.transaction;version="[3,4)",org.springframework.transaction.s
 upport;version="[3,4)",org.springframework.util;version="[3,4)",org.w3c
 .dom


So I would need to figure out in our marvelous build system, to make
it use the old behavior, so it can use the correct version ranges.





On Mon, Oct 29, 2012 at 10:57 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Hi
>
> If I remember correctly, yesterday that was also one of my suspections as
> well so that I reverted locally back to 4.2, however still observing the
> same behaviour.
> Also tried downgrading felix-compendium, felix-configadmin and
> felix-framework versions back to what they were before the upgrade to OSGi
> 4.3 and still no change in the behaviour.
>
> I suspect the OSGi POM settings being broken *before* this OSGi upgrade,
> like <camel.osgi.import.defaults> and whatnot.
>
> Babak
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Builds-on-Jenkins-tp5721653p5721717.html
> Sent from the Camel Development mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Builds on Jenkins

Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi

If I remember correctly, yesterday that was also one of my suspections as
well so that I reverted locally back to 4.2, however still observing the
same behaviour.
Also tried downgrading felix-compendium, felix-configadmin and
felix-framework versions back to what they were before the upgrade to OSGi
4.3 and still no change in the behaviour.

I suspect the OSGi POM settings being broken *before* this OSGi upgrade,
like <camel.osgi.import.defaults> and whatnot.

Babak




--
View this message in context: http://camel.465427.n5.nabble.com/Builds-on-Jenkins-tp5721653p5721717.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Builds on Jenkins

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

I suspect its OSGi framework 4.2 -> 4.3 that is not backwards compatible.
Have not checked it, but seems like the code changes in
camel-core-osgi I assume was needed during the upgrade.
And if so, it may be that we are not binary backwards compatible.

As a temporary workaround we could downgrade to 4.2. But we would need
to come up with a solution so we can upgrade Camel.
As OSGi R5 is out, and we are only on 4.2.


On Sun, Oct 28, 2012 at 11:05 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Hi
>
> Currently all the OSGi integration tests I tried fail as well with the
> same root cause and as we disable these tests on the CI-Servers we don't
> spot the problem there.
>
> I digged pretty long into it but couldn't find the problem. Needs some
> OSGi experts to look into it.
>
> There was also a new test by camel-gson on the trunk failing continuously
> by some profiles which I've already fixed.
>
> Following a sample itest failing:
>
> ~/dev/workspace/camel/tests/camel-itest-osgi>mvn test -Dtest=FileRouteTest
> Š
> Š
> java.lang.Exception: Could not start bundle
> mvn:org.apache.camel/camel-core/2.11-SNAPSHOT in feature(s)
> camel-core-2.11-SNAPSHOT: Activator start error in bundle
> org.apache.camel.camel-core [67].
>         at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Feat
> uresServiceImpl.java:356)[21:org.apache.karaf.features.core:2.2.9]
>         at
> org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServic
> eImpl.java:988)[21:org.apache.karaf.features.core:2.2.9]
> Caused by: org.osgi.framework.BundleException: Activator start error in
> bundle org.apache.camel.camel-core [67].
>         at
> org.apache.felix.framework.Felix.activateBundle(Felix.java:1951)[org.apache
> .felix.framework-3.2.2.jar:]
>         at
> org.apache.felix.framework.Felix.startBundle(Felix.java:1822)[org.apache.fe
> lix.framework-3.2.2.jar:]
>         at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:927)[org.apache
> .felix.framework-3.2.2.jar:]
>         at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:914)[org.apache
> .felix.framework-3.2.2.jar:]
>         at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Feat
> uresServiceImpl.java:353)[21:org.apache.karaf.features.core:2.2.9]
>         ... 1 more
> Caused by: java.lang.NoClassDefFoundError:
> org/osgi/framework/BundleActivator
>         at java.lang.ClassLoader.defineClass1(Native Method)[:1.6.0_32]
>         at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)[:1.6.0_32]
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:615)[:1.6.0_32]
>         at
> org.apache.felix.framework.ModuleImpl$ModuleClassLoader.findClass(ModuleImp
> l.java:1947)
>         at
> org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(Modul
> eImpl.java:752)
>         at org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:72)
>         at
> org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImp
> l.java:1807)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:247)[:1.6.0_32]
>         at
> org.apache.felix.framework.ModuleImpl.getClassByDelegation(ModuleImpl.java:
> 670)
>         at org.apache.felix.framework.Felix.createBundleActivator(Felix.java:3808)
>         at org.apache.felix.framework.Felix.activateBundle(Felix.java:1899)
>         ... 5 more
> Caused by: java.lang.ClassNotFoundException:
> org.osgi.framework.BundleActivator not found by
> org.apache.camel.camel-core [67]
>         at
> org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(Modul
> eImpl.java:812)[org.apache.felix.framework-3.2.2.jar:]
>         at
> org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:72)[org.ap
> ache.felix.framework-3.2.2.jar:]
>         at
> org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImp
> l.java:1807)[org.apache.felix.framework-3.2.2.jar:]
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:247)[:1.6.0_32]
>         ... 16 more
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.687 sec
> <<< FAILURE!
>
> Babak
>
>
> Am 27.10.12 23:07 schrieb "Christian Müller" unter
> <ch...@gmail.com>:
>
>>At present, many of our builds at Jenkins fail [0] and it looks like they
>>are not stable. Some of the build are failing since three or more weeks.
>>This is really bad.
>>Let's reserve some time to fix this and bring the Camel builds back to
>>stable. Assign one of the issues to yourself and work on it.
>>
>>[0] https://builds.apache.org/view/A-F/view/Camel/
>>[1] https://issues.apache.org/jira/browse/CAMEL-5749
>>[2] https://issues.apache.org/jira/browse/CAMEL-5750
>>[3] https://issues.apache.org/jira/browse/CAMEL-5751
>>[4] https://issues.apache.org/jira/browse/CAMEL-5752
>>[5] https://issues.apache.org/jira/browse/CAMEL-5753
>>
>>Thanks in advance,
>>Christian
>>
>>--
>
>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Builds on Jenkins

Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi

Currently all the OSGi integration tests I tried fail as well with the
same root cause and as we disable these tests on the CI-Servers we don't
spot the problem there.

I digged pretty long into it but couldn't find the problem. Needs some
OSGi experts to look into it.

There was also a new test by camel-gson on the trunk failing continuously
by some profiles which I've already fixed.

Following a sample itest failing:
 
~/dev/workspace/camel/tests/camel-itest-osgi>mvn test -Dtest=FileRouteTest
Š
Š
java.lang.Exception: Could not start bundle
mvn:org.apache.camel/camel-core/2.11-SNAPSHOT in feature(s)
camel-core-2.11-SNAPSHOT: Activator start error in bundle
org.apache.camel.camel-core [67].
	at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Feat
uresServiceImpl.java:356)[21:org.apache.karaf.features.core:2.2.9]
	at 
org.apache.karaf.features.internal.FeaturesServiceImpl$1.run(FeaturesServic
eImpl.java:988)[21:org.apache.karaf.features.core:2.2.9]
Caused by: org.osgi.framework.BundleException: Activator start error in
bundle org.apache.camel.camel-core [67].
	at 
org.apache.felix.framework.Felix.activateBundle(Felix.java:1951)[org.apache
.felix.framework-3.2.2.jar:]
	at 
org.apache.felix.framework.Felix.startBundle(Felix.java:1822)[org.apache.fe
lix.framework-3.2.2.jar:]
	at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:927)[org.apache
.felix.framework-3.2.2.jar:]
	at 
org.apache.felix.framework.BundleImpl.start(BundleImpl.java:914)[org.apache
.felix.framework-3.2.2.jar:]
	at 
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Feat
uresServiceImpl.java:353)[21:org.apache.karaf.features.core:2.2.9]
	... 1 more
Caused by: java.lang.NoClassDefFoundError:
org/osgi/framework/BundleActivator
	at java.lang.ClassLoader.defineClass1(Native Method)[:1.6.0_32]
	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)[:1.6.0_32]
	at java.lang.ClassLoader.defineClass(ClassLoader.java:615)[:1.6.0_32]
	at 
org.apache.felix.framework.ModuleImpl$ModuleClassLoader.findClass(ModuleImp
l.java:1947)
	at 
org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(Modul
eImpl.java:752)
	at org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:72)
	at 
org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImp
l.java:1807)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)[:1.6.0_32]
	at 
org.apache.felix.framework.ModuleImpl.getClassByDelegation(ModuleImpl.java:
670)
	at org.apache.felix.framework.Felix.createBundleActivator(Felix.java:3808)
	at org.apache.felix.framework.Felix.activateBundle(Felix.java:1899)
	... 5 more
Caused by: java.lang.ClassNotFoundException:
org.osgi.framework.BundleActivator not found by
org.apache.camel.camel-core [67]
	at 
org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(Modul
eImpl.java:812)[org.apache.felix.framework-3.2.2.jar:]
	at 
org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:72)[org.ap
ache.felix.framework-3.2.2.jar:]
	at 
org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImp
l.java:1807)[org.apache.felix.framework-3.2.2.jar:]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)[:1.6.0_32]
	... 16 more
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.687 sec
<<< FAILURE!

Babak


Am 27.10.12 23:07 schrieb "Christian Müller" unter
<ch...@gmail.com>:

>At present, many of our builds at Jenkins fail [0] and it looks like they
>are not stable. Some of the build are failing since three or more weeks.
>This is really bad.
>Let's reserve some time to fix this and bring the Camel builds back to
>stable. Assign one of the issues to yourself and work on it.
>
>[0] https://builds.apache.org/view/A-F/view/Camel/
>[1] https://issues.apache.org/jira/browse/CAMEL-5749
>[2] https://issues.apache.org/jira/browse/CAMEL-5750
>[3] https://issues.apache.org/jira/browse/CAMEL-5751
>[4] https://issues.apache.org/jira/browse/CAMEL-5752
>[5] https://issues.apache.org/jira/browse/CAMEL-5753
>
>Thanks in advance,
>Christian
>
>--