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/04/26 20:59:23 UTC
Whirr-Ubuntu - Build # 333 - Failure
The Apache Jenkins build system has built Whirr-Ubuntu (build #333)
Status: Failure
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/333/ to view the results.
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0' available
I am wondering where the version '0.0.0' comes from in the stacktrace.
Do we need to do some kind of cleanup?
On Fri, May 4, 2012 at 6:15 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
> I have no idea. I am not yet familiar with Karaf. Ioannes, do you have an idea?
>
> On Fri, May 4, 2012 at 6:02 PM, Andrei Savu <sa...@gmail.com> wrote:
>> Good catch. Any ideas how to fix it?
>> On May 4, 2012 6:57 PM, "Frank Scholten" <fr...@frankscholten.nl> wrote:
>>
>>> I commented out all services in WhirrServicesTest except pig-client
>>> and now I see different stacktraces such as 'port already in use' and
>>> 'Unable to intialize bean rmiRegistryFactory'
>>>
>>> See
>>>
>>>
>>> https://builds.apache.org/view/S-Z/view/Whirr/job/Whirr-Ubuntu/343/org.apache.whirr.karaf$itests/testReport/org.apache.whirr.karaf.itest/WhirrServicesTest/testServices_WhirrServicesTest_testServices_KarafTestContainer_mvn_org_apache_karaf__apache_karaf__2_2_5__tar_gz_/
>>>
>>> On Thu, May 3, 2012 at 3:51 AM, Ioannis Canellos <io...@gmail.com>
>>> wrote:
>>> > This looks strange. The only think I can currnently think of is the
>>> > artifact not getting installed and thus using an older verison of the
>>> > feature descriptor.
>>> >
>>> >
>>> > --
>>> > *Ioannis Canellos*
>>> > *
>>> > FuseSource <http://fusesource.com>
>>> >
>>> > **
>>> > Blog: http://iocanel.blogspot.com
>>> > **
>>> > Twitter: iocanel
>>> > *
>>>
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
I have no idea. I am not yet familiar with Karaf. Ioannes, do you have an idea?
On Fri, May 4, 2012 at 6:02 PM, Andrei Savu <sa...@gmail.com> wrote:
> Good catch. Any ideas how to fix it?
> On May 4, 2012 6:57 PM, "Frank Scholten" <fr...@frankscholten.nl> wrote:
>
>> I commented out all services in WhirrServicesTest except pig-client
>> and now I see different stacktraces such as 'port already in use' and
>> 'Unable to intialize bean rmiRegistryFactory'
>>
>> See
>>
>>
>> https://builds.apache.org/view/S-Z/view/Whirr/job/Whirr-Ubuntu/343/org.apache.whirr.karaf$itests/testReport/org.apache.whirr.karaf.itest/WhirrServicesTest/testServices_WhirrServicesTest_testServices_KarafTestContainer_mvn_org_apache_karaf__apache_karaf__2_2_5__tar_gz_/
>>
>> On Thu, May 3, 2012 at 3:51 AM, Ioannis Canellos <io...@gmail.com>
>> wrote:
>> > This looks strange. The only think I can currnently think of is the
>> > artifact not getting installed and thus using an older verison of the
>> > feature descriptor.
>> >
>> >
>> > --
>> > *Ioannis Canellos*
>> > *
>> > FuseSource <http://fusesource.com>
>> >
>> > **
>> > Blog: http://iocanel.blogspot.com
>> > **
>> > Twitter: iocanel
>> > *
>>
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
Good catch. Any ideas how to fix it?
On May 4, 2012 6:57 PM, "Frank Scholten" <fr...@frankscholten.nl> wrote:
> I commented out all services in WhirrServicesTest except pig-client
> and now I see different stacktraces such as 'port already in use' and
> 'Unable to intialize bean rmiRegistryFactory'
>
> See
>
>
> https://builds.apache.org/view/S-Z/view/Whirr/job/Whirr-Ubuntu/343/org.apache.whirr.karaf$itests/testReport/org.apache.whirr.karaf.itest/WhirrServicesTest/testServices_WhirrServicesTest_testServices_KarafTestContainer_mvn_org_apache_karaf__apache_karaf__2_2_5__tar_gz_/
>
> On Thu, May 3, 2012 at 3:51 AM, Ioannis Canellos <io...@gmail.com>
> wrote:
> > This looks strange. The only think I can currnently think of is the
> > artifact not getting installed and thus using an older verison of the
> > feature descriptor.
> >
> >
> > --
> > *Ioannis Canellos*
> > *
> > FuseSource <http://fusesource.com>
> >
> > **
> > Blog: http://iocanel.blogspot.com
> > **
> > Twitter: iocanel
> > *
>
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
I commented out all services in WhirrServicesTest except pig-client
and now I see different stacktraces such as 'port already in use' and
'Unable to intialize bean rmiRegistryFactory'
See
https://builds.apache.org/view/S-Z/view/Whirr/job/Whirr-Ubuntu/343/org.apache.whirr.karaf$itests/testReport/org.apache.whirr.karaf.itest/WhirrServicesTest/testServices_WhirrServicesTest_testServices_KarafTestContainer_mvn_org_apache_karaf__apache_karaf__2_2_5__tar_gz_/
On Thu, May 3, 2012 at 3:51 AM, Ioannis Canellos <io...@gmail.com> wrote:
> This looks strange. The only think I can currnently think of is the
> artifact not getting installed and thus using an older verison of the
> feature descriptor.
>
>
> --
> *Ioannis Canellos*
> *
> FuseSource <http://fusesource.com>
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Ioannis Canellos <io...@gmail.com>.
This looks strange. The only think I can currnently think of is the
artifact not getting installed and thus using an older verison of the
feature descriptor.
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
I am also not authorised. Try to either create an issue
at https://issues.apache.org/jira/browse/INFRA or ping
the infra guys on IRC at #asfinfra.
-- Andrei
On Wed, May 2, 2012 at 2:46 PM, Frank Scholten <fr...@frankscholten.nl>wrote:
> Andrei,
>
> I removed the pig-client to get back to a stable situation but now the
> build is running for a few hours and hangs on the whirr-puppet module.
> How can we stop it? I can log into Jenkins but am not authorized to
> stop a build.
>
> Cheers,
>
> Frank
>
> On Fri, Apr 27, 2012 at 1:04 AM, Andrei Savu <sa...@gmail.com>
> wrote:
> > I think this is not a timing issue. This is the relevant stack trace:
> >
> > Ioannis any ideas? I've checked the .xml files a few times already.
> >
> >
> > features:install whirr-pig
> > java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0'
> available
> > at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)
> > at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> > at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)
> > at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> > at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> > at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
> > at
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
> > at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
> > at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> > at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> > at
> org.apache.whirr.karaf.itest.WhirrKarafTestSupport$1.call(WhirrKarafTestSupport.java:127)
> > at
> org.apache.whirr.karaf.itest.WhirrKarafTestSupport$1.call(WhirrKarafTestSupport.java:120)
> > at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> > at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> > at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> > at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > at java.lang.Thread.run(Thread.java:662)
> >
> >
> > -- Andrei Savu / axemblr.com / Tools for Clouds
> >
> > On Fri, Apr 27, 2012 at 1:56 AM, Apache Jenkins Server <
> > jenkins@builds.apache.org> wrote:
> >
> >> The Apache Jenkins build system has built Whirr-Ubuntu (build #334)
> >>
> >> Status: Still Failing
> >>
> >> Check console output at
> https://builds.apache.org/job/Whirr-Ubuntu/334/to view the results.
>
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Frank Scholten <fr...@frankscholten.nl>.
Andrei,
I removed the pig-client to get back to a stable situation but now the
build is running for a few hours and hangs on the whirr-puppet module.
How can we stop it? I can log into Jenkins but am not authorized to
stop a build.
Cheers,
Frank
On Fri, Apr 27, 2012 at 1:04 AM, Andrei Savu <sa...@gmail.com> wrote:
> I think this is not a timing issue. This is the relevant stack trace:
>
> Ioannis any ideas? I've checked the .xml files a few times already.
>
>
> features:install whirr-pig
> java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0' available
> at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)
> at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)
> at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
> at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
> at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at org.apache.whirr.karaf.itest.WhirrKarafTestSupport$1.call(WhirrKarafTestSupport.java:127)
> at org.apache.whirr.karaf.itest.WhirrKarafTestSupport$1.call(WhirrKarafTestSupport.java:120)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
> -- Andrei Savu / axemblr.com / Tools for Clouds
>
> On Fri, Apr 27, 2012 at 1:56 AM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> The Apache Jenkins build system has built Whirr-Ubuntu (build #334)
>>
>> Status: Still Failing
>>
>> Check console output at https://builds.apache.org/job/Whirr-Ubuntu/334/to view the results.
Re: Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Andrei Savu <sa...@gmail.com>.
I think this is not a timing issue. This is the relevant stack trace:
Ioannis any ideas? I've checked the .xml files a few times already.
features:install whirr-pig
java.lang.Exception: No feature named 'whirr-pig' with version '0.0.0' available
at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:276)
at org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
at org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)
at org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:38)
at org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)
at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:474)
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:400)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
at org.apache.whirr.karaf.itest.WhirrKarafTestSupport$1.call(WhirrKarafTestSupport.java:127)
at org.apache.whirr.karaf.itest.WhirrKarafTestSupport$1.call(WhirrKarafTestSupport.java:120)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
-- Andrei Savu / axemblr.com / Tools for Clouds
On Fri, Apr 27, 2012 at 1:56 AM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> The Apache Jenkins build system has built Whirr-Ubuntu (build #334)
>
> Status: Still Failing
>
> Check console output at https://builds.apache.org/job/Whirr-Ubuntu/334/to view the results.
Whirr-Ubuntu - Build # 334 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Whirr-Ubuntu (build #334)
Status: Still Failing
Check console output at https://builds.apache.org/job/Whirr-Ubuntu/334/ to view the results.