You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2012/03/12 16:17:42 UTC
Whirr-Ubuntu - Build # 320 - Still Failing
The Apache Jenkins build system has built Whirr-Ubuntu (build #320)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/320/ to view the results.
Whirr-Ubuntu - Build # 328 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #328)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/328/ to view the results.
Whirr-Ubuntu - Build # 327 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #327)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/327/ to view the results.
Whirr-Ubuntu - Build # 326 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #326)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/326/ to view the results.
Whirr-Ubuntu - Build # 325 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #325)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/325/ to view the results.
Whirr-Ubuntu - Build # 324 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #324)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/324/ to view the results.
Whirr-Ubuntu - Build # 323 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #323)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/323/ to view the results.
Whirr-Ubuntu - Build # 322 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #322)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/322/ to view the results.
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
It's worth trying. I'm out of ideas.
On Thu, Apr 26, 2012 at 10:29 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
> The WhirrServicesTest which currently fails on Jenkins works on my machine.
>
> Shall we double the SERVICE_TIMEOUT?
>
> Frank
>
> On Fri, Mar 23, 2012 at 6:41 PM, Andrei Savu <sa...@gmail.com>
> wrote:
> > I hope a bigger timeout will make all this go away. I will add this as
> part
> > of WHIRR-504.
> >
> > On Thu, Mar 22, 2012 at 7:15 PM, Frank Scholten <frank@frankscholten.nl
> >wrote:
> >
> >> When I run the integration tests locally I get all sorts of exceptions
> >>
> >> Caused by: java.lang.AssertionError: Expected bundle to be started
> >> expected:<32> but was:<2>
> >>
> >> Caused by: org.osgi.framework.BundleException: Unresolved constraint
> >> in bundle jclouds-sshj [67]: Unable to resolve 67.0: missing
> >> requirement [67.0] package;
> >> (&(package=org.jclouds.compute.domain)(version>=1.3.1))
> >>
> >> features:install whirr-mahout
> >> java.lang.Exception: Could not start bundle
> >> mvn:org.jclouds.driver/jclouds-sshj/1.3.1 in feature(s)
> >> jclouds-driver-sshj-1.3.1: Unresolved constraint in bundle
> >> jclouds-sshj [67]: Unable to resolve 67.0: missing requirement [67.0]
> >> package; (&(package=org.jclouds.compute.domain)(version>=1.3.1))
> >>
> >> and more.
> >>
> >> I also get the one we see on Jenkins
> >>
> >> features:install whirr-pig
> >> java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0'
> >> available
> >>
> >> Frank
> >>
> >> On Tue, Mar 13, 2012 at 10:34 PM, Andrei Savu <sa...@gmail.com>
> >> wrote:
> >> > On Tue, Mar 13, 2012 at 11:22 PM, Frank Scholten <
> frank@frankscholten.nl
> >> >wrote:
> >> >
> >> >> The exception also says it's waiting for the service. Could we maybe
> >> >> extent the timeout?
> >> >>
> >> >
> >> > I guess that's something we can try. It's strange that it's only
> >> happening
> >> > for this service
> >> > we've added recently. Do you see the exception on your machine?
> >>
>
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
The WhirrServicesTest which currently fails on Jenkins works on my machine.
Shall we double the SERVICE_TIMEOUT?
Frank
On Fri, Mar 23, 2012 at 6:41 PM, Andrei Savu <sa...@gmail.com> wrote:
> I hope a bigger timeout will make all this go away. I will add this as part
> of WHIRR-504.
>
> On Thu, Mar 22, 2012 at 7:15 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
>
>> When I run the integration tests locally I get all sorts of exceptions
>>
>> Caused by: java.lang.AssertionError: Expected bundle to be started
>> expected:<32> but was:<2>
>>
>> Caused by: org.osgi.framework.BundleException: Unresolved constraint
>> in bundle jclouds-sshj [67]: Unable to resolve 67.0: missing
>> requirement [67.0] package;
>> (&(package=org.jclouds.compute.domain)(version>=1.3.1))
>>
>> features:install whirr-mahout
>> java.lang.Exception: Could not start bundle
>> mvn:org.jclouds.driver/jclouds-sshj/1.3.1 in feature(s)
>> jclouds-driver-sshj-1.3.1: Unresolved constraint in bundle
>> jclouds-sshj [67]: Unable to resolve 67.0: missing requirement [67.0]
>> package; (&(package=org.jclouds.compute.domain)(version>=1.3.1))
>>
>> and more.
>>
>> I also get the one we see on Jenkins
>>
>> features:install whirr-pig
>> java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0'
>> available
>>
>> Frank
>>
>> On Tue, Mar 13, 2012 at 10:34 PM, Andrei Savu <sa...@gmail.com>
>> wrote:
>> > On Tue, Mar 13, 2012 at 11:22 PM, Frank Scholten <frank@frankscholten.nl
>> >wrote:
>> >
>> >> The exception also says it's waiting for the service. Could we maybe
>> >> extent the timeout?
>> >>
>> >
>> > I guess that's something we can try. It's strange that it's only
>> happening
>> > for this service
>> > we've added recently. Do you see the exception on your machine?
>>
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
I hope a bigger timeout will make all this go away. I will add this as part
of WHIRR-504.
On Thu, Mar 22, 2012 at 7:15 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
> When I run the integration tests locally I get all sorts of exceptions
>
> Caused by: java.lang.AssertionError: Expected bundle to be started
> expected:<32> but was:<2>
>
> Caused by: org.osgi.framework.BundleException: Unresolved constraint
> in bundle jclouds-sshj [67]: Unable to resolve 67.0: missing
> requirement [67.0] package;
> (&(package=org.jclouds.compute.domain)(version>=1.3.1))
>
> features:install whirr-mahout
> java.lang.Exception: Could not start bundle
> mvn:org.jclouds.driver/jclouds-sshj/1.3.1 in feature(s)
> jclouds-driver-sshj-1.3.1: Unresolved constraint in bundle
> jclouds-sshj [67]: Unable to resolve 67.0: missing requirement [67.0]
> package; (&(package=org.jclouds.compute.domain)(version>=1.3.1))
>
> and more.
>
> I also get the one we see on Jenkins
>
> features:install whirr-pig
> java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0'
> available
>
> Frank
>
> On Tue, Mar 13, 2012 at 10:34 PM, Andrei Savu <sa...@gmail.com>
> wrote:
> > On Tue, Mar 13, 2012 at 11:22 PM, Frank Scholten <frank@frankscholten.nl
> >wrote:
> >
> >> The exception also says it's waiting for the service. Could we maybe
> >> extent the timeout?
> >>
> >
> > I guess that's something we can try. It's strange that it's only
> happening
> > for this service
> > we've added recently. Do you see the exception on your machine?
>
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
When I run the integration tests locally I get all sorts of exceptions
Caused by: java.lang.AssertionError: Expected bundle to be started
expected:<32> but was:<2>
Caused by: org.osgi.framework.BundleException: Unresolved constraint
in bundle jclouds-sshj [67]: Unable to resolve 67.0: missing
requirement [67.0] package;
(&(package=org.jclouds.compute.domain)(version>=1.3.1))
features:install whirr-mahout
java.lang.Exception: Could not start bundle
mvn:org.jclouds.driver/jclouds-sshj/1.3.1 in feature(s)
jclouds-driver-sshj-1.3.1: Unresolved constraint in bundle
jclouds-sshj [67]: Unable to resolve 67.0: missing requirement [67.0]
package; (&(package=org.jclouds.compute.domain)(version>=1.3.1))
and more.
I also get the one we see on Jenkins
features:install whirr-pig
java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0' available
Frank
On Tue, Mar 13, 2012 at 10:34 PM, Andrei Savu <sa...@gmail.com> wrote:
> On Tue, Mar 13, 2012 at 11:22 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
>
>> The exception also says it's waiting for the service. Could we maybe
>> extent the timeout?
>>
>
> I guess that's something we can try. It's strange that it's only happening
> for this service
> we've added recently. Do you see the exception on your machine?
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
On Tue, Mar 13, 2012 at 11:22 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
> The exception also says it's waiting for the service. Could we maybe
> extent the timeout?
>
I guess that's something we can try. It's strange that it's only happening
for this service
we've added recently. Do you see the exception on your machine?
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
The exception also says it's waiting for the service. Could we maybe
extent the timeout?
Frank
On Tue, Mar 13, 2012 at 10:09 PM, Andrei Savu <sa...@gmail.com> wrote:
> Right but I am unable to reproduce the failure outside the build server.
> Tried on a vanilla OS install (in Amazon) and it builds as expected from
> trunk.
>
> -- Andrei Savu
>
> On Tue, Mar 13, 2012 at 11:07 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
>
>> The build still fails with the exception:
>>
>> java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0'
>> available
>>
>> I am not that familiar with Karaf but any idea why it mentions version
>> '0.0.0'? Should be 0.8.0-SNAPSHOT right?
>>
>> Frank
>>
>> On Mon, Mar 12, 2012 at 5:30 PM, Apache Jenkins Server
>> <je...@builds.apache.org> wrote:
>> > The Apache Jenkins build system has built Whirr-Ubuntu (build #321)
>> >
>> > Status: Still Failing
>> >
>> > Check console output at https://builds.apache.org/job/Whirr-Ubuntu/321/to view the results.
>>
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
Right but I am unable to reproduce the failure outside the build server.
Tried on a vanilla OS install (in Amazon) and it builds as expected from
trunk.
-- Andrei Savu
On Tue, Mar 13, 2012 at 11:07 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
> The build still fails with the exception:
>
> java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0'
> available
>
> I am not that familiar with Karaf but any idea why it mentions version
> '0.0.0'? Should be 0.8.0-SNAPSHOT right?
>
> Frank
>
> On Mon, Mar 12, 2012 at 5:30 PM, Apache Jenkins Server
> <je...@builds.apache.org> wrote:
> > The Apache Jenkins build system has built Whirr-Ubuntu (build #321)
> >
> > Status: Still Failing
> >
> > Check console output at https://builds.apache.org/job/Whirr-Ubuntu/321/to view the results.
>
Re: Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
The build still fails with the exception:
java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0' available
I am not that familiar with Karaf but any idea why it mentions version
'0.0.0'? Should be 0.8.0-SNAPSHOT right?
Frank
On Mon, Mar 12, 2012 at 5:30 PM, Apache Jenkins Server
<je...@builds.apache.org> wrote:
> The Apache Jenkins build system has built Whirr-Ubuntu (build #321)
>
> Status: Still Failing
>
> Check console output at https://builds.apache.org/job/Whirr-Ubuntu/321/ to view the results.
Whirr-Ubuntu - Build # 321 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #321)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/321/ to view the results.