camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Cosentino <ancosen1...@yahoo.com.INVALID>
Subject Re: Re: CamelBeanValidatorTest is failing
Date Thu, 07 Sep 2017 06:46:02 GMT
No, it's not related to the Karaf feature.

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd




 
 
 On Thursday, September 7, 2017, 4:53:50 AM GMT+2, Tadayoshi Sato <sato.tadayoshi@gmail.com>
wrote: 





Hi Andrea,

Yeah, it doesn't reproduce locally in my laptop, either.

The last commit that the camel-itest-karaf ran successfully on Jenkins was
this on Aug 1:
https://github.com/apache/camel/commit/0b243a48aea3f30fba8460c7b26f7b184b3c6456
so it could be that any changes that were committed right after the commit
may have caused the itest failures. (It's also possible that any external
factors such as changes on the maven central repo that happened right after
Aug 1  could have caused it though.)

However the original failed build history #2210 is already gone on Jenkins:
https://builds.apache.org/job/Camel.trunk.itest.karaf/
so it's hard to detect which one is the culprit.

I found this ticket. Was this itest failure the original motivation for the
task?
https://issues.apache.org/jira/browse/CAMEL-11650


On Thu, Sep 7, 2017 at 10:24 AM, Tadayoshi Sato <sato.tadayoshi@gmail.com>
wrote:

> Filed the JIRA: https://issues.apache.org/jira/browse/CAMEL-11758
> I'll look into it.
>
> On Wed, Sep 6, 2017 at 3:02 PM, Andrea Cosentino <ancosen1985@yahoo.com>
> wrote:
>
>> Tested locally it seems to work.
>>
>> [org.ops4j.store.intern.TemporaryStore] : Exit store():
>> 8e7251cf3141ec0862eb074f2466f6df6820a6d0
>> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Preparing and
>> Installing bundle (from stream )..
>> [org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient] : Packing
>> probe into memory for true RMI. Hopefully things will fill in..
>> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Installed bundle
>> (from stream) as ID: 80
>> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : call
>> [[TestAddress:PaxExam-d99f7da4-022e-4e50-8778-4ec519603761
>> root:PaxExam-5408707c-548d-485f-b49e-98d07bdbbdfc]]
>> [org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer] :
>> Shutting down the test container (Pax Runner)
>> [org.ops4j.pax.exam.spi.reactors.ReactorManager] : suite finished
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.461
>> sec - in org.apache.camel.itest.karaf.CamelBeanValidatorTest
>>
>>
>>
>> --
>> Andrea Cosentino
>> ----------------------------------
>> Apache Camel PMC Member
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: ancosen1985@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, September 6, 2017, 6:43:22 AM GMT+2, Tadayoshi Sato <
>> sato.tadayoshi@gmail.com> wrote:
>>
>>
>>
>>
>>
>> Looks like CamelBeanValidatorTest in camel-itest-karaf is failing:
>>
>> https://builds.apache.org/job/Camel.trunk.itest.karaf/2397/console
>>
>>
>> Tests in error:
>>  CamelBeanValidatorTest.test » WrappedTestContainer
>> [test(org.apache.camel.ites...
>>
>>
>> Best regards,
>> Tadayoshi
>>
>>
>


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