camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ayache Khettar <ayache.khet...@googlemail.com>
Subject Re: CamelBlueprintTest randomly failing tests
Date Tue, 17 Feb 2015 11:30:12 GMT
I've added the
https://github.com/akhettar/message-connector/blob/master/test/MHSTestFixture.java
incase you want to see the parent test class.
On 17 February 2015 at 11:15, Ayache Khettar <ayache.khettar@googlemail.com>
wrote:

> Here is sample project: https://github.com/akhettar/message-connector.
> There are other component failings too, but randomly and not frequently.
> But it's becoming really annoying to see these random failures happening 4
> to 6 times a day (depending on how often we check in). Rarely fails on my
> dev machine.
>
> Thanks
>
> Ayache
>
>
> On 17 February 2015 at 10:55, Grzegorz Grzybek <gr.grzybek@gmail.com>
> wrote:
>
>> Ayache, could you share it? via github maybe?
>>
>> ~Grzegorz
>>
>> 2015-02-17 11:54 GMT+01:00 Ayache Khettar <ayache.khettar@googlemail.com
>> >:
>>
>> > My own Unit Test
>> >
>> > Ayache
>> > On 17 February 2015 at 10:42, Grzegorz Grzybek <gr.grzybek@gmail.com>
>> > wrote:
>> >
>> > > Ayache - do you try to run one of Camel's own tests, or your own?
>> > >
>> > > regards
>> > > Grzegorz
>> > >
>> > > 2015-02-17 11:35 GMT+01:00 Ayache Khettar <
>> ayache.khettar@googlemail.com
>> > >:
>> > >
>> > > > Hi Grzegorz
>> > > >
>> > > > I am using Camel version 2.13.2, which I think it should have the
>> fixe
>> > > you
>> > > > pointed below.
>> > > >
>> > > > Thanks
>> > > >
>> > > > Ayache
>> > > >
>> > > > On 17 February 2015 at 08:58, Grzegorz Grzybek <
>> gr.grzybek@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Hi Ayache, what version of Camel do you use?
>> > > > >
>> > > > > There was a fix to camel-blueprint tests a while ago (see
>> > > > > https://issues.apache.org/jira/browse/CAMEL-7469)
>> > > > >
>> > > > > regards
>> > > > > Grzegorz Grzybek
>> > > > >
>> > > > > 2015-02-17 9:39 GMT+01:00 Willem Jiang <willem.jiang@gmail.com>:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > Does your QA box have the internet access?
>> > > > > >
>> > > > > > --
>> > > > > > Willem Jiang
>> > > > > >
>> > > > > > Red Hat, Inc.
>> > > > > > Web: http://www.redhat.com
>> > > > > > Blog: http://willemjiang.blogspot.com (English)
>> > > > > > http://jnn.iteye.com (Chinese)
>> > > > > > Twitter: willemjiang
>> > > > > > Weibo: 姜宁willem
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On February 6, 2015 at 6:35:47 PM, Ayache Khettar (
>> > > > > > ayache.khettar@googlemail.com) wrote:
>> > > > > > > Hi
>> > > > > > >
>> > > > > > >
>> > > > > > > I am seeing random Unit tests failures - see below.
These
>> > failures
>> > > > are
>> > > > > > > happening randomly on QA box (bit slower than dev machines).
>> > Looks
>> > > > > > > like the test hangs waiting for namespace handlers
- see
>> below.
>> > > > > > >
>> > > > > > >
>> > > > > > > I am testing camel blueprint using CamelBlueprintTests.
Has
>> > anyone
>> > > > > > > experienced such issue?
>> > > > > > >
>> > > > > > >
>> > > > > > > Regards,
>> > > > > > >
>> > > > > > >
>> > > > > > > Ayache
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > Blueprint Extender: 1] BlueprintContainerImpl INFO
Bundle
>> > > > > > > BlueprintTest is waiting for namespace handlers
>> > > > > > > [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > java.lang.RuntimeException: Gave up waiting for service
>> > > > > > > (objectClass=org.apache.camel.CamelContext)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(CamelBlueprintHelper.java:240)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(CamelBlueprintHelper.java:202)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createCamelContext(CamelBlueprintTestSupport.java:352)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:247)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:217)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:183)
>> > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > > > > > > at java.lang.reflect.Method.invoke(Method.java:606)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>> > > > > > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>> > > > > > > at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>> > > > > > > at
>> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>> > > > > > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>> > > > > > > at
>> > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>> > > > > > > at
>> > > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>> > > > > > > at
>> > org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>> > > > > > > at
>> > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>> > > > > > > at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>> > > > > > > at
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>> > > > > > > at
>> > > > > >
>> > > >
>> >
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message