[UPDATE] MavenTest itest fails randomly but often

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[UPDATE] MavenTest itest fails randomly but often

jbonofre
Hi guys,

Our Jenkins jobs are not very stable (both master and PR) due to the MavenTest
which randomly fails (but often).

I will remove this test from master and move it to a dedicated PR to investigate
(but at least it won't impact our nightly builds and PRs).

Regards
JB
--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

ggerla
Hi JB
what type of failure?

Regards
Giuseppe





2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:

> Hi guys,
>
> Our Jenkins jobs are not very stable (both master and PR) due to the
> MavenTest which randomly fails (but often).
>
> I will remove this test from master and move it to a dedicated PR to
> investigate (but at least it won't impact our nightly builds and PRs).
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
Hi,

randomly (only for this itest), the container never came up (pax exam).

Regards
JB

On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:

> Hi JB
> what type of failure?
>
> Regards
> Giuseppe
>
>
>
>
>
> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
>> Hi guys,
>>
>> Our Jenkins jobs are not very stable (both master and PR) due to the
>> MavenTest which randomly fails (but often).
>>
>> I will remove this test from master and move it to a dedicated PR to
>> investigate (but at least it won't impact our nightly builds and PRs).
>>
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

ggerla
Hi JB
If you remember i had the same problem.
After several week and several investigativo, i discovered some difference
beteeen my itest and activemq itest. So i changed my itest sturtup. Now It
seems solved.


Regards
Giuseppe


Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha scritto:

> Hi,
>
> randomly (only for this itest), the container never came up (pax exam).
>
> Regards
> JB
>
> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>
>> Hi JB
>> what type of failure?
>>
>> Regards
>> Giuseppe
>>
>>
>>
>>
>>
>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>
>> Hi guys,
>>>
>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>> MavenTest which randomly fails (but often).
>>>
>>> I will remove this test from master and move it to a dedicated PR to
>>> investigate (but at least it won't impact our nightly builds and PRs).
>>>
>>> Regards
>>> JB
>>> --
>>> Jean-Baptiste Onofré
>>> [hidden email]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
Hi Giuseppe,

not sure I follow you. You mean you change the itest on your local copy ?

Regards
JB

On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:

> Hi JB
> If you remember i had the same problem.
> After several week and several investigativo, i discovered some difference
> beteeen my itest and activemq itest. So i changed my itest sturtup. Now It
> seems solved.
>
>
> Regards
> Giuseppe
>
>
> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha scritto:
>
>> Hi,
>>
>> randomly (only for this itest), the container never came up (pax exam).
>>
>> Regards
>> JB
>>
>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>
>>> Hi JB
>>> what type of failure?
>>>
>>> Regards
>>> Giuseppe
>>>
>>>
>>>
>>>
>>>
>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>
>>> Hi guys,
>>>>
>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>> MavenTest which randomly fails (but often).
>>>>
>>>> I will remove this test from master and move it to a dedicated PR to
>>>> investigate (but at least it won't impact our nightly builds and PRs).
>>>>
>>>> Regards
>>>> JB
>>>> --
>>>> Jean-Baptiste Onofré
>>>> [hidden email]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

ggerla
Hi JB
although the tests worked on my PC, very often they went wrong on the
jenkins machine.
I did several experiments to find the problem, but it was very difficult to
understand it.
What I understood is that for some reason the container is too slow to come
up and the timeout of pax expired before. Why? I don't know.
At the end, I clone the activemq project on the jenkins machine, I start a
build and it works. So I did a diff between activemq itest configuration
and my itest configuration. The result was that I removed some
initialization from my itest:

        customOptions.add(junitBundles());
        customOptions.add(KarafDistributionOption
            .editConfigurationFilePut("etc/org.apache.karaf.features.cfg",
"featuresBoot",
                                      "(aries-blueprint, bundle, config,
deployer, diagnostic, feature, instance, jaas, kar, log, management,
package, service, shell, shell-compat, ssh, system, wrap)"));

then also:

       MavenUrlReference karafStandardRepo =
maven().groupId("org.apache.karaf.features")

.artifactId("standard").classifier("features").type("xml").versionAsInProject();

 customOptions.add(KarafDistributionOption.features(karafStandardRepo,
"scr"));

and I replaced "activemq-broker-noweb" feature with "activemq" one.
I rememeber that also surefire plugin version has a rule in this problem.
So I changed my poms as following:

PARENT-POM


 <surefire.plugin.version>2.16</surefire.plugin.version>
                               <pluginManagement>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${surefire.plugin.version}</version>
<configuration>
<excludes>
<exclude>**/*AcceptanceTest.java</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</pluginManagement>



ITEST-PROJECT-POM

                        <plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<forkCount>1</forkCount>
<reuseForks>false</reuseForks>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
<argLine>-Xmx512m</argLine>
<excludes>
</excludes>
<systemPropertyVariables>
<activemqVersion>${activemq.version}</activemqVersion>
<karafVersion>${karaf.version}</karafVersion>
</systemPropertyVariables>
</configuration>
</plugin>


I hope this can help you.


Regards
Giuseppe








2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:

> Hi Giuseppe,
>
> not sure I follow you. You mean you change the itest on your local copy ?
>
> Regards
> JB
>
>
> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>
>> Hi JB
>> If you remember i had the same problem.
>> After several week and several investigativo, i discovered some difference
>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now It
>> seems solved.
>>
>>
>> Regards
>> Giuseppe
>>
>>
>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>> scritto:
>>
>> Hi,
>>>
>>> randomly (only for this itest), the container never came up (pax exam).
>>>
>>> Regards
>>> JB
>>>
>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>
>>> Hi JB
>>>> what type of failure?
>>>>
>>>> Regards
>>>> Giuseppe
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>
>>>> Hi guys,
>>>>
>>>>>
>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>> MavenTest which randomly fails (but often).
>>>>>
>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>> investigate (but at least it won't impact our nightly builds and PRs).
>>>>>
>>>>> Regards
>>>>> JB
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> [hidden email]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
Hmm, not sure it's related as we use the same KarafTestSupport in bunch of other
itest.

I will exclude the MavenTest for now, and investigate.

Thanks anyway !

Regards
JB

On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:

> Hi JB
> although the tests worked on my PC, very often they went wrong on the
> jenkins machine.
> I did several experiments to find the problem, but it was very difficult to
> understand it.
> What I understood is that for some reason the container is too slow to come
> up and the timeout of pax expired before. Why? I don't know.
> At the end, I clone the activemq project on the jenkins machine, I start a
> build and it works. So I did a diff between activemq itest configuration
> and my itest configuration. The result was that I removed some
> initialization from my itest:
>
>          customOptions.add(junitBundles());
>          customOptions.add(KarafDistributionOption
>              .editConfigurationFilePut("etc/org.apache.karaf.features.cfg",
> "featuresBoot",
>                                        "(aries-blueprint, bundle, config,
> deployer, diagnostic, feature, instance, jaas, kar, log, management,
> package, service, shell, shell-compat, ssh, system, wrap)"));
>
> then also:
>
>         MavenUrlReference karafStandardRepo =
> maven().groupId("org.apache.karaf.features")
>
> .artifactId("standard").classifier("features").type("xml").versionAsInProject();
>
>   customOptions.add(KarafDistributionOption.features(karafStandardRepo,
> "scr"));
>
> and I replaced "activemq-broker-noweb" feature with "activemq" one.
> I rememeber that also surefire plugin version has a rule in this problem.
> So I changed my poms as following:
>
> PARENT-POM
>
>
>   <surefire.plugin.version>2.16</surefire.plugin.version>
>                                 <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>${surefire.plugin.version}</version>
> <configuration>
> <excludes>
> <exclude>**/*AcceptanceTest.java</exclude>
> </excludes>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
>
>
>
> ITEST-PROJECT-POM
>
>                          <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <forkCount>1</forkCount>
> <reuseForks>false</reuseForks>
> <redirectTestOutputToFile>true</redirectTestOutputToFile>
> <argLine>-Xmx512m</argLine>
> <excludes>
> </excludes>
> <systemPropertyVariables>
> <activemqVersion>${activemq.version}</activemqVersion>
> <karafVersion>${karaf.version}</karafVersion>
> </systemPropertyVariables>
> </configuration>
> </plugin>
>
>
> I hope this can help you.
>
>
> Regards
> Giuseppe
>
>
>
>
>
>
>
>
> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
>> Hi Giuseppe,
>>
>> not sure I follow you. You mean you change the itest on your local copy ?
>>
>> Regards
>> JB
>>
>>
>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>
>>> Hi JB
>>> If you remember i had the same problem.
>>> After several week and several investigativo, i discovered some difference
>>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now It
>>> seems solved.
>>>
>>>
>>> Regards
>>> Giuseppe
>>>
>>>
>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>> scritto:
>>>
>>> Hi,
>>>>
>>>> randomly (only for this itest), the container never came up (pax exam).
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>
>>>> Hi JB
>>>>> what type of failure?
>>>>>
>>>>> Regards
>>>>> Giuseppe
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>
>>>>> Hi guys,
>>>>>
>>>>>>
>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>> MavenTest which randomly fails (but often).
>>>>>>
>>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>>> investigate (but at least it won't impact our nightly builds and PRs).
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>> --
>>>>>> Jean-Baptiste Onofré
>>>>>> [hidden email]
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> [hidden email]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Grzegorz Grzybek
Hello

I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
I'd love to investigate the exact cause, but didn't have time yet...
The surefire/failsafe issue is
https://issues.apache.org/jira/browse/SUREFIRE-1374

And in my (jboss fuse) integration tests I stayed with 2.19.x.

regards
Grzegorz Grzybek

2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:

> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
> other itest.
>
> I will exclude the MavenTest for now, and investigate.
>
> Thanks anyway !
>
> Regards
> JB
>
>
> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>
>> Hi JB
>> although the tests worked on my PC, very often they went wrong on the
>> jenkins machine.
>> I did several experiments to find the problem, but it was very difficult
>> to
>> understand it.
>> What I understood is that for some reason the container is too slow to
>> come
>> up and the timeout of pax expired before. Why? I don't know.
>> At the end, I clone the activemq project on the jenkins machine, I start a
>> build and it works. So I did a diff between activemq itest configuration
>> and my itest configuration. The result was that I removed some
>> initialization from my itest:
>>
>>          customOptions.add(junitBundles());
>>          customOptions.add(KarafDistributionOption
>>              .editConfigurationFilePut("etc/org.apache.karaf.features.cf
>> g",
>> "featuresBoot",
>>                                        "(aries-blueprint, bundle, config,
>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>
>> then also:
>>
>>         MavenUrlReference karafStandardRepo =
>> maven().groupId("org.apache.karaf.features")
>>
>> .artifactId("standard").classifier("features").type("xml").
>> versionAsInProject();
>>
>>   customOptions.add(KarafDistributionOption.features(karafStandardRepo,
>> "scr"));
>>
>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>> I rememeber that also surefire plugin version has a rule in this problem.
>> So I changed my poms as following:
>>
>> PARENT-POM
>>
>>
>>   <surefire.plugin.version>2.16</surefire.plugin.version>
>>                                 <pluginManagement>
>> <plugins>
>> <plugin>
>> <artifactId>maven-surefire-plugin</artifactId>
>> <version>${surefire.plugin.version}</version>
>> <configuration>
>> <excludes>
>> <exclude>**/*AcceptanceTest.java</exclude>
>> </excludes>
>> </configuration>
>> </plugin>
>> </plugins>
>> </pluginManagement>
>>
>>
>>
>> ITEST-PROJECT-POM
>>
>>                          <plugin>
>> <artifactId>maven-surefire-plugin</artifactId>
>> <configuration>
>> <forkCount>1</forkCount>
>> <reuseForks>false</reuseForks>
>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>> <argLine>-Xmx512m</argLine>
>> <excludes>
>> </excludes>
>> <systemPropertyVariables>
>> <activemqVersion>${activemq.version}</activemqVersion>
>> <karafVersion>${karaf.version}</karafVersion>
>> </systemPropertyVariables>
>> </configuration>
>> </plugin>
>>
>>
>> I hope this can help you.
>>
>>
>> Regards
>> Giuseppe
>>
>>
>>
>>
>>
>>
>>
>>
>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>
>> Hi Giuseppe,
>>>
>>> not sure I follow you. You mean you change the itest on your local copy ?
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>
>>> Hi JB
>>>> If you remember i had the same problem.
>>>> After several week and several investigativo, i discovered some
>>>> difference
>>>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now
>>>> It
>>>> seems solved.
>>>>
>>>>
>>>> Regards
>>>> Giuseppe
>>>>
>>>>
>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>> scritto:
>>>>
>>>> Hi,
>>>>
>>>>>
>>>>> randomly (only for this itest), the container never came up (pax exam).
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>
>>>>> Hi JB
>>>>>
>>>>>> what type of failure?
>>>>>>
>>>>>> Regards
>>>>>> Giuseppe
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>>
>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>
>>>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>> PRs).
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>> --
>>>>>>> Jean-Baptiste Onofré
>>>>>>> [hidden email]
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> [hidden email]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Achim Nierbeck
Hi Grzegorz,

interesting that you have issues with that version.
I just updated pax-web to use 2.20.1 and all tests are passing (finally)

regards, Achim

2017-11-27 8:28 GMT+01:00 Grzegorz Grzybek <[hidden email]>:

> Hello
>
> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
> I'd love to investigate the exact cause, but didn't have time yet...
> The surefire/failsafe issue is
> https://issues.apache.org/jira/browse/SUREFIRE-1374
>
> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>
> regards
> Grzegorz Grzybek
>
> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
> > Hmm, not sure it's related as we use the same KarafTestSupport in bunch
> of
> > other itest.
> >
> > I will exclude the MavenTest for now, and investigate.
> >
> > Thanks anyway !
> >
> > Regards
> > JB
> >
> >
> > On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
> >
> >> Hi JB
> >> although the tests worked on my PC, very often they went wrong on the
> >> jenkins machine.
> >> I did several experiments to find the problem, but it was very difficult
> >> to
> >> understand it.
> >> What I understood is that for some reason the container is too slow to
> >> come
> >> up and the timeout of pax expired before. Why? I don't know.
> >> At the end, I clone the activemq project on the jenkins machine, I
> start a
> >> build and it works. So I did a diff between activemq itest configuration
> >> and my itest configuration. The result was that I removed some
> >> initialization from my itest:
> >>
> >>          customOptions.add(junitBundles());
> >>          customOptions.add(KarafDistributionOption
> >>              .editConfigurationFilePut("etc/org.apache.karaf.features.
> cf
> >> g",
> >> "featuresBoot",
> >>                                        "(aries-blueprint, bundle,
> config,
> >> deployer, diagnostic, feature, instance, jaas, kar, log, management,
> >> package, service, shell, shell-compat, ssh, system, wrap)"));
> >>
> >> then also:
> >>
> >>         MavenUrlReference karafStandardRepo =
> >> maven().groupId("org.apache.karaf.features")
> >>
> >> .artifactId("standard").classifier("features").type("xml").
> >> versionAsInProject();
> >>
> >>   customOptions.add(KarafDistributionOption.features(karafStandardRepo,
> >> "scr"));
> >>
> >> and I replaced "activemq-broker-noweb" feature with "activemq" one.
> >> I rememeber that also surefire plugin version has a rule in this
> problem.
> >> So I changed my poms as following:
> >>
> >> PARENT-POM
> >>
> >>
> >>   <surefire.plugin.version>2.16</surefire.plugin.version>
> >>                                 <pluginManagement>
> >> <plugins>
> >> <plugin>
> >> <artifactId>maven-surefire-plugin</artifactId>
> >> <version>${surefire.plugin.version}</version>
> >> <configuration>
> >> <excludes>
> >> <exclude>**/*AcceptanceTest.java</exclude>
> >> </excludes>
> >> </configuration>
> >> </plugin>
> >> </plugins>
> >> </pluginManagement>
> >>
> >>
> >>
> >> ITEST-PROJECT-POM
> >>
> >>                          <plugin>
> >> <artifactId>maven-surefire-plugin</artifactId>
> >> <configuration>
> >> <forkCount>1</forkCount>
> >> <reuseForks>false</reuseForks>
> >> <redirectTestOutputToFile>true</redirectTestOutputToFile>
> >> <argLine>-Xmx512m</argLine>
> >> <excludes>
> >> </excludes>
> >> <systemPropertyVariables>
> >> <activemqVersion>${activemq.version}</activemqVersion>
> >> <karafVersion>${karaf.version}</karafVersion>
> >> </systemPropertyVariables>
> >> </configuration>
> >> </plugin>
> >>
> >>
> >> I hope this can help you.
> >>
> >>
> >> Regards
> >> Giuseppe
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> >>
> >> Hi Giuseppe,
> >>>
> >>> not sure I follow you. You mean you change the itest on your local
> copy ?
> >>>
> >>> Regards
> >>> JB
> >>>
> >>>
> >>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
> >>>
> >>> Hi JB
> >>>> If you remember i had the same problem.
> >>>> After several week and several investigativo, i discovered some
> >>>> difference
> >>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
> Now
> >>>> It
> >>>> seems solved.
> >>>>
> >>>>
> >>>> Regards
> >>>> Giuseppe
> >>>>
> >>>>
> >>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
> >>>> scritto:
> >>>>
> >>>> Hi,
> >>>>
> >>>>>
> >>>>> randomly (only for this itest), the container never came up (pax
> exam).
> >>>>>
> >>>>> Regards
> >>>>> JB
> >>>>>
> >>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
> >>>>>
> >>>>> Hi JB
> >>>>>
> >>>>>> what type of failure?
> >>>>>>
> >>>>>> Regards
> >>>>>> Giuseppe
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> >>>>>>
> >>>>>> Hi guys,
> >>>>>>
> >>>>>>
> >>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to
> the
> >>>>>>> MavenTest which randomly fails (but often).
> >>>>>>>
> >>>>>>> I will remove this test from master and move it to a dedicated PR
> to
> >>>>>>> investigate (but at least it won't impact our nightly builds and
> >>>>>>> PRs).
> >>>>>>>
> >>>>>>> Regards
> >>>>>>> JB
> >>>>>>> --
> >>>>>>> Jean-Baptiste Onofré
> >>>>>>> [hidden email]
> >>>>>>> http://blog.nanthrax.net
> >>>>>>> Talend - http://www.talend.com
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>
> >>>>> Jean-Baptiste Onofré
> >>>>> [hidden email]
> >>>>> http://blog.nanthrax.net
> >>>>> Talend - http://www.talend.com
> >>>>>
> >>>>>
> >>>>>
> >>>> --
> >>> Jean-Baptiste Onofré
> >>> [hidden email]
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>>
> >>>
> >>
> > --
> > Jean-Baptiste Onofré
> > [hidden email]
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>



--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Grzegorz Grzybek
Hmm, I didn't check 2.20.1, rather 2.20. But if anything goes wrong, I
think there still may be some surefire issue.

regards
Grzegorz

2017-11-27 8:37 GMT+01:00 Achim Nierbeck <[hidden email]>:

> Hi Grzegorz,
>
> interesting that you have issues with that version.
> I just updated pax-web to use 2.20.1 and all tests are passing (finally)
>
> regards, Achim
>
> 2017-11-27 8:28 GMT+01:00 Grzegorz Grzybek <[hidden email]>:
>
> > Hello
> >
> > I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
> > I'd love to investigate the exact cause, but didn't have time yet...
> > The surefire/failsafe issue is
> > https://issues.apache.org/jira/browse/SUREFIRE-1374
> >
> > And in my (jboss fuse) integration tests I stayed with 2.19.x.
> >
> > regards
> > Grzegorz Grzybek
> >
> > 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> >
> > > Hmm, not sure it's related as we use the same KarafTestSupport in bunch
> > of
> > > other itest.
> > >
> > > I will exclude the MavenTest for now, and investigate.
> > >
> > > Thanks anyway !
> > >
> > > Regards
> > > JB
> > >
> > >
> > > On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
> > >
> > >> Hi JB
> > >> although the tests worked on my PC, very often they went wrong on the
> > >> jenkins machine.
> > >> I did several experiments to find the problem, but it was very
> difficult
> > >> to
> > >> understand it.
> > >> What I understood is that for some reason the container is too slow to
> > >> come
> > >> up and the timeout of pax expired before. Why? I don't know.
> > >> At the end, I clone the activemq project on the jenkins machine, I
> > start a
> > >> build and it works. So I did a diff between activemq itest
> configuration
> > >> and my itest configuration. The result was that I removed some
> > >> initialization from my itest:
> > >>
> > >>          customOptions.add(junitBundles());
> > >>          customOptions.add(KarafDistributionOption
> > >>              .editConfigurationFilePut("
> etc/org.apache.karaf.features.
> > cf
> > >> g",
> > >> "featuresBoot",
> > >>                                        "(aries-blueprint, bundle,
> > config,
> > >> deployer, diagnostic, feature, instance, jaas, kar, log, management,
> > >> package, service, shell, shell-compat, ssh, system, wrap)"));
> > >>
> > >> then also:
> > >>
> > >>         MavenUrlReference karafStandardRepo =
> > >> maven().groupId("org.apache.karaf.features")
> > >>
> > >> .artifactId("standard").classifier("features").type("xml").
> > >> versionAsInProject();
> > >>
> > >>   customOptions.add(KarafDistributionOption.
> features(karafStandardRepo,
> > >> "scr"));
> > >>
> > >> and I replaced "activemq-broker-noweb" feature with "activemq" one.
> > >> I rememeber that also surefire plugin version has a rule in this
> > problem.
> > >> So I changed my poms as following:
> > >>
> > >> PARENT-POM
> > >>
> > >>
> > >>   <surefire.plugin.version>2.16</surefire.plugin.version>
> > >>                                 <pluginManagement>
> > >> <plugins>
> > >> <plugin>
> > >> <artifactId>maven-surefire-plugin</artifactId>
> > >> <version>${surefire.plugin.version}</version>
> > >> <configuration>
> > >> <excludes>
> > >> <exclude>**/*AcceptanceTest.java</exclude>
> > >> </excludes>
> > >> </configuration>
> > >> </plugin>
> > >> </plugins>
> > >> </pluginManagement>
> > >>
> > >>
> > >>
> > >> ITEST-PROJECT-POM
> > >>
> > >>                          <plugin>
> > >> <artifactId>maven-surefire-plugin</artifactId>
> > >> <configuration>
> > >> <forkCount>1</forkCount>
> > >> <reuseForks>false</reuseForks>
> > >> <redirectTestOutputToFile>true</redirectTestOutputToFile>
> > >> <argLine>-Xmx512m</argLine>
> > >> <excludes>
> > >> </excludes>
> > >> <systemPropertyVariables>
> > >> <activemqVersion>${activemq.version}</activemqVersion>
> > >> <karafVersion>${karaf.version}</karafVersion>
> > >> </systemPropertyVariables>
> > >> </configuration>
> > >> </plugin>
> > >>
> > >>
> > >> I hope this can help you.
> > >>
> > >>
> > >> Regards
> > >> Giuseppe
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> > >>
> > >> Hi Giuseppe,
> > >>>
> > >>> not sure I follow you. You mean you change the itest on your local
> > copy ?
> > >>>
> > >>> Regards
> > >>> JB
> > >>>
> > >>>
> > >>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
> > >>>
> > >>> Hi JB
> > >>>> If you remember i had the same problem.
> > >>>> After several week and several investigativo, i discovered some
> > >>>> difference
> > >>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
> > Now
> > >>>> It
> > >>>> seems solved.
> > >>>>
> > >>>>
> > >>>> Regards
> > >>>> Giuseppe
> > >>>>
> > >>>>
> > >>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
> > >>>> scritto:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>>>
> > >>>>> randomly (only for this itest), the container never came up (pax
> > exam).
> > >>>>>
> > >>>>> Regards
> > >>>>> JB
> > >>>>>
> > >>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
> > >>>>>
> > >>>>> Hi JB
> > >>>>>
> > >>>>>> what type of failure?
> > >>>>>>
> > >>>>>> Regards
> > >>>>>> Giuseppe
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> > >>>>>>
> > >>>>>> Hi guys,
> > >>>>>>
> > >>>>>>
> > >>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to
> > the
> > >>>>>>> MavenTest which randomly fails (but often).
> > >>>>>>>
> > >>>>>>> I will remove this test from master and move it to a dedicated PR
> > to
> > >>>>>>> investigate (but at least it won't impact our nightly builds and
> > >>>>>>> PRs).
> > >>>>>>>
> > >>>>>>> Regards
> > >>>>>>> JB
> > >>>>>>> --
> > >>>>>>> Jean-Baptiste Onofré
> > >>>>>>> [hidden email]
> > >>>>>>> http://blog.nanthrax.net
> > >>>>>>> Talend - http://www.talend.com
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>
> > >>>>> Jean-Baptiste Onofré
> > >>>>> [hidden email]
> > >>>>> http://blog.nanthrax.net
> > >>>>> Talend - http://www.talend.com
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>> --
> > >>> Jean-Baptiste Onofré
> > >>> [hidden email]
> > >>> http://blog.nanthrax.net
> > >>> Talend - http://www.talend.com
> > >>>
> > >>>
> > >>
> > > --
> > > Jean-Baptiste Onofré
> > > [hidden email]
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
> >
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
In reply to this post by Grzegorz Grzybek
Yeah, I remember I got issues with surefire.

However, I don't think it's related in that case (different issue).

So, let me exclude this test for now to give us time to investigate.

Regards
JB

On 11/27/2017 08:28 AM, Grzegorz Grzybek wrote:

> Hello
>
> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
> I'd love to investigate the exact cause, but didn't have time yet...
> The surefire/failsafe issue is
> https://issues.apache.org/jira/browse/SUREFIRE-1374
>
> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>
> regards
> Grzegorz Grzybek
>
> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
>> other itest.
>>
>> I will exclude the MavenTest for now, and investigate.
>>
>> Thanks anyway !
>>
>> Regards
>> JB
>>
>>
>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>
>>> Hi JB
>>> although the tests worked on my PC, very often they went wrong on the
>>> jenkins machine.
>>> I did several experiments to find the problem, but it was very difficult
>>> to
>>> understand it.
>>> What I understood is that for some reason the container is too slow to
>>> come
>>> up and the timeout of pax expired before. Why? I don't know.
>>> At the end, I clone the activemq project on the jenkins machine, I start a
>>> build and it works. So I did a diff between activemq itest configuration
>>> and my itest configuration. The result was that I removed some
>>> initialization from my itest:
>>>
>>>           customOptions.add(junitBundles());
>>>           customOptions.add(KarafDistributionOption
>>>               .editConfigurationFilePut("etc/org.apache.karaf.features.cf
>>> g",
>>> "featuresBoot",
>>>                                         "(aries-blueprint, bundle, config,
>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>
>>> then also:
>>>
>>>          MavenUrlReference karafStandardRepo =
>>> maven().groupId("org.apache.karaf.features")
>>>
>>> .artifactId("standard").classifier("features").type("xml").
>>> versionAsInProject();
>>>
>>>    customOptions.add(KarafDistributionOption.features(karafStandardRepo,
>>> "scr"));
>>>
>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>> I rememeber that also surefire plugin version has a rule in this problem.
>>> So I changed my poms as following:
>>>
>>> PARENT-POM
>>>
>>>
>>>    <surefire.plugin.version>2.16</surefire.plugin.version>
>>>                                  <pluginManagement>
>>> <plugins>
>>> <plugin>
>>> <artifactId>maven-surefire-plugin</artifactId>
>>> <version>${surefire.plugin.version}</version>
>>> <configuration>
>>> <excludes>
>>> <exclude>**/*AcceptanceTest.java</exclude>
>>> </excludes>
>>> </configuration>
>>> </plugin>
>>> </plugins>
>>> </pluginManagement>
>>>
>>>
>>>
>>> ITEST-PROJECT-POM
>>>
>>>                           <plugin>
>>> <artifactId>maven-surefire-plugin</artifactId>
>>> <configuration>
>>> <forkCount>1</forkCount>
>>> <reuseForks>false</reuseForks>
>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>> <argLine>-Xmx512m</argLine>
>>> <excludes>
>>> </excludes>
>>> <systemPropertyVariables>
>>> <activemqVersion>${activemq.version}</activemqVersion>
>>> <karafVersion>${karaf.version}</karafVersion>
>>> </systemPropertyVariables>
>>> </configuration>
>>> </plugin>
>>>
>>>
>>> I hope this can help you.
>>>
>>>
>>> Regards
>>> Giuseppe
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>
>>> Hi Giuseppe,
>>>>
>>>> not sure I follow you. You mean you change the itest on your local copy ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>
>>>> Hi JB
>>>>> If you remember i had the same problem.
>>>>> After several week and several investigativo, i discovered some
>>>>> difference
>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now
>>>>> It
>>>>> seems solved.
>>>>>
>>>>>
>>>>> Regards
>>>>> Giuseppe
>>>>>
>>>>>
>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>> scritto:
>>>>>
>>>>> Hi,
>>>>>
>>>>>>
>>>>>> randomly (only for this itest), the container never came up (pax exam).
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>
>>>>>> Hi JB
>>>>>>
>>>>>>> what type of failure?
>>>>>>>
>>>>>>> Regards
>>>>>>> Giuseppe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>
>>>>>>> Hi guys,
>>>>>>>
>>>>>>>
>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>
>>>>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>> PRs).
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>> --
>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> [hidden email]
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>
>>>>>> Jean-Baptiste Onofré
>>>>>> [hidden email]
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> [hidden email]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
I found something interesting: MavenTest doesn't extend KarafTestSupport. So,
I'm checking the difference between the config in KarafTestSupport (where all
tests pass without problem) and the config in MavenTest.

I'm on it and keep you posted ;)

Regards
JB

On 11/27/2017 09:18 AM, Jean-Baptiste Onofré wrote:

> Yeah, I remember I got issues with surefire.
>
> However, I don't think it's related in that case (different issue).
>
> So, let me exclude this test for now to give us time to investigate.
>
> Regards
> JB
>
> On 11/27/2017 08:28 AM, Grzegorz Grzybek wrote:
>> Hello
>>
>> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
>> I'd love to investigate the exact cause, but didn't have time yet...
>> The surefire/failsafe issue is
>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>
>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>
>> regards
>> Grzegorz Grzybek
>>
>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>
>>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
>>> other itest.
>>>
>>> I will exclude the MavenTest for now, and investigate.
>>>
>>> Thanks anyway !
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>
>>>> Hi JB
>>>> although the tests worked on my PC, very often they went wrong on the
>>>> jenkins machine.
>>>> I did several experiments to find the problem, but it was very difficult
>>>> to
>>>> understand it.
>>>> What I understood is that for some reason the container is too slow to
>>>> come
>>>> up and the timeout of pax expired before. Why? I don't know.
>>>> At the end, I clone the activemq project on the jenkins machine, I start a
>>>> build and it works. So I did a diff between activemq itest configuration
>>>> and my itest configuration. The result was that I removed some
>>>> initialization from my itest:
>>>>
>>>>           customOptions.add(junitBundles());
>>>>           customOptions.add(KarafDistributionOption
>>>>               .editConfigurationFilePut("etc/org.apache.karaf.features.cf
>>>> g",
>>>> "featuresBoot",
>>>>                                         "(aries-blueprint, bundle, config,
>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>
>>>> then also:
>>>>
>>>>          MavenUrlReference karafStandardRepo =
>>>> maven().groupId("org.apache.karaf.features")
>>>>
>>>> .artifactId("standard").classifier("features").type("xml").
>>>> versionAsInProject();
>>>>
>>>>    customOptions.add(KarafDistributionOption.features(karafStandardRepo,
>>>> "scr"));
>>>>
>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>> I rememeber that also surefire plugin version has a rule in this problem.
>>>> So I changed my poms as following:
>>>>
>>>> PARENT-POM
>>>>
>>>>
>>>>    <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>                                  <pluginManagement>
>>>> <plugins>
>>>> <plugin>
>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>> <version>${surefire.plugin.version}</version>
>>>> <configuration>
>>>> <excludes>
>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>> </excludes>
>>>> </configuration>
>>>> </plugin>
>>>> </plugins>
>>>> </pluginManagement>
>>>>
>>>>
>>>>
>>>> ITEST-PROJECT-POM
>>>>
>>>>                           <plugin>
>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>> <configuration>
>>>> <forkCount>1</forkCount>
>>>> <reuseForks>false</reuseForks>
>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>> <argLine>-Xmx512m</argLine>
>>>> <excludes>
>>>> </excludes>
>>>> <systemPropertyVariables>
>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>> <karafVersion>${karaf.version}</karafVersion>
>>>> </systemPropertyVariables>
>>>> </configuration>
>>>> </plugin>
>>>>
>>>>
>>>> I hope this can help you.
>>>>
>>>>
>>>> Regards
>>>> Giuseppe
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>
>>>> Hi Giuseppe,
>>>>>
>>>>> not sure I follow you. You mean you change the itest on your local copy ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>
>>>>> Hi JB
>>>>>> If you remember i had the same problem.
>>>>>> After several week and several investigativo, i discovered some
>>>>>> difference
>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now
>>>>>> It
>>>>>> seems solved.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Giuseppe
>>>>>>
>>>>>>
>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>> scritto:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>>
>>>>>>> randomly (only for this itest), the container never came up (pax exam).
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>
>>>>>>> Hi JB
>>>>>>>
>>>>>>>> what type of failure?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Giuseppe
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>>
>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>
>>>>>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>> PRs).
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>> --
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>> [hidden email]
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>
>>>>>>> Jean-Baptiste Onofré
>>>>>>> [hidden email]
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>
>>> --
>>> Jean-Baptiste Onofré
>>> [hidden email]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Grzegorz Grzybek
MavenTest was my non-KarafTestSupport test case. I wanted to be able to
configure Maven resolver and Jetty server to test timeouts, http proxies,
etc.

regards
Grzegorz Grzybek

2017-11-27 10:52 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:

> I found something interesting: MavenTest doesn't extend KarafTestSupport.
> So, I'm checking the difference between the config in KarafTestSupport
> (where all tests pass without problem) and the config in MavenTest.
>
> I'm on it and keep you posted ;)
>
> Regards
> JB
>
>
> On 11/27/2017 09:18 AM, Jean-Baptiste Onofré wrote:
>
>> Yeah, I remember I got issues with surefire.
>>
>> However, I don't think it's related in that case (different issue).
>>
>> So, let me exclude this test for now to give us time to investigate.
>>
>> Regards
>> JB
>>
>> On 11/27/2017 08:28 AM, Grzegorz Grzybek wrote:
>>
>>> Hello
>>>
>>> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
>>> I'd love to investigate the exact cause, but didn't have time yet...
>>> The surefire/failsafe issue is
>>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>>
>>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>>
>>> regards
>>> Grzegorz Grzybek
>>>
>>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>
>>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch
>>>> of
>>>> other itest.
>>>>
>>>> I will exclude the MavenTest for now, and investigate.
>>>>
>>>> Thanks anyway !
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>>
>>>> Hi JB
>>>>> although the tests worked on my PC, very often they went wrong on the
>>>>> jenkins machine.
>>>>> I did several experiments to find the problem, but it was very
>>>>> difficult
>>>>> to
>>>>> understand it.
>>>>> What I understood is that for some reason the container is too slow to
>>>>> come
>>>>> up and the timeout of pax expired before. Why? I don't know.
>>>>> At the end, I clone the activemq project on the jenkins machine, I
>>>>> start a
>>>>> build and it works. So I did a diff between activemq itest
>>>>> configuration
>>>>> and my itest configuration. The result was that I removed some
>>>>> initialization from my itest:
>>>>>
>>>>>           customOptions.add(junitBundles());
>>>>>           customOptions.add(KarafDistributionOption
>>>>>               .editConfigurationFilePut("etc/
>>>>> org.apache.karaf.features.cf
>>>>> g",
>>>>> "featuresBoot",
>>>>>                                         "(aries-blueprint, bundle,
>>>>> config,
>>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>>
>>>>> then also:
>>>>>
>>>>>          MavenUrlReference karafStandardRepo =
>>>>> maven().groupId("org.apache.karaf.features")
>>>>>
>>>>> .artifactId("standard").classifier("features").type("xml").
>>>>> versionAsInProject();
>>>>>
>>>>>    customOptions.add(KarafDistributionOption.features(
>>>>> karafStandardRepo,
>>>>> "scr"));
>>>>>
>>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>>> I rememeber that also surefire plugin version has a rule in this
>>>>> problem.
>>>>> So I changed my poms as following:
>>>>>
>>>>> PARENT-POM
>>>>>
>>>>>
>>>>>    <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>>                                  <pluginManagement>
>>>>> <plugins>
>>>>> <plugin>
>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>> <version>${surefire.plugin.version}</version>
>>>>> <configuration>
>>>>> <excludes>
>>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>>> </excludes>
>>>>> </configuration>
>>>>> </plugin>
>>>>> </plugins>
>>>>> </pluginManagement>
>>>>>
>>>>>
>>>>>
>>>>> ITEST-PROJECT-POM
>>>>>
>>>>>                           <plugin>
>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>> <configuration>
>>>>> <forkCount>1</forkCount>
>>>>> <reuseForks>false</reuseForks>
>>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>>> <argLine>-Xmx512m</argLine>
>>>>> <excludes>
>>>>> </excludes>
>>>>> <systemPropertyVariables>
>>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>>> <karafVersion>${karaf.version}</karafVersion>
>>>>> </systemPropertyVariables>
>>>>> </configuration>
>>>>> </plugin>
>>>>>
>>>>>
>>>>> I hope this can help you.
>>>>>
>>>>>
>>>>> Regards
>>>>> Giuseppe
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>
>>>>> Hi Giuseppe,
>>>>>
>>>>>>
>>>>>> not sure I follow you. You mean you change the itest on your local
>>>>>> copy ?
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>>
>>>>>> Hi JB
>>>>>>
>>>>>>> If you remember i had the same problem.
>>>>>>> After several week and several investigativo, i discovered some
>>>>>>> difference
>>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
>>>>>>> Now
>>>>>>> It
>>>>>>> seems solved.
>>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>> Giuseppe
>>>>>>>
>>>>>>>
>>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>>> scritto:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>> randomly (only for this itest), the container never came up (pax
>>>>>>>> exam).
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>>
>>>>>>>> Hi JB
>>>>>>>>
>>>>>>>> what type of failure?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> Giuseppe
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>>
>>>>>>>>> Hi guys,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to
>>>>>>>>>> the
>>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>>
>>>>>>>>>> I will remove this test from master and move it to a dedicated PR
>>>>>>>>>> to
>>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>>> PRs).
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> JB
>>>>>>>>>> --
>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>>> [hidden email]
>>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> [hidden email]
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>
>>>>>> Jean-Baptiste Onofré
>>>>>> [hidden email]
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> [hidden email]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
I know, but I'm checking if there is no missing config.

Regards
JB

On 11/27/2017 11:40 AM, Grzegorz Grzybek wrote:

> MavenTest was my non-KarafTestSupport test case. I wanted to be able to
> configure Maven resolver and Jetty server to test timeouts, http proxies,
> etc.
>
> regards
> Grzegorz Grzybek
>
> 2017-11-27 10:52 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
>> I found something interesting: MavenTest doesn't extend KarafTestSupport.
>> So, I'm checking the difference between the config in KarafTestSupport
>> (where all tests pass without problem) and the config in MavenTest.
>>
>> I'm on it and keep you posted ;)
>>
>> Regards
>> JB
>>
>>
>> On 11/27/2017 09:18 AM, Jean-Baptiste Onofré wrote:
>>
>>> Yeah, I remember I got issues with surefire.
>>>
>>> However, I don't think it's related in that case (different issue).
>>>
>>> So, let me exclude this test for now to give us time to investigate.
>>>
>>> Regards
>>> JB
>>>
>>> On 11/27/2017 08:28 AM, Grzegorz Grzybek wrote:
>>>
>>>> Hello
>>>>
>>>> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
>>>> I'd love to investigate the exact cause, but didn't have time yet...
>>>> The surefire/failsafe issue is
>>>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>>>
>>>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>>>
>>>> regards
>>>> Grzegorz Grzybek
>>>>
>>>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>
>>>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch
>>>>> of
>>>>> other itest.
>>>>>
>>>>> I will exclude the MavenTest for now, and investigate.
>>>>>
>>>>> Thanks anyway !
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>>>
>>>>> Hi JB
>>>>>> although the tests worked on my PC, very often they went wrong on the
>>>>>> jenkins machine.
>>>>>> I did several experiments to find the problem, but it was very
>>>>>> difficult
>>>>>> to
>>>>>> understand it.
>>>>>> What I understood is that for some reason the container is too slow to
>>>>>> come
>>>>>> up and the timeout of pax expired before. Why? I don't know.
>>>>>> At the end, I clone the activemq project on the jenkins machine, I
>>>>>> start a
>>>>>> build and it works. So I did a diff between activemq itest
>>>>>> configuration
>>>>>> and my itest configuration. The result was that I removed some
>>>>>> initialization from my itest:
>>>>>>
>>>>>>            customOptions.add(junitBundles());
>>>>>>            customOptions.add(KarafDistributionOption
>>>>>>                .editConfigurationFilePut("etc/
>>>>>> org.apache.karaf.features.cf
>>>>>> g",
>>>>>> "featuresBoot",
>>>>>>                                          "(aries-blueprint, bundle,
>>>>>> config,
>>>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>>>
>>>>>> then also:
>>>>>>
>>>>>>           MavenUrlReference karafStandardRepo =
>>>>>> maven().groupId("org.apache.karaf.features")
>>>>>>
>>>>>> .artifactId("standard").classifier("features").type("xml").
>>>>>> versionAsInProject();
>>>>>>
>>>>>>     customOptions.add(KarafDistributionOption.features(
>>>>>> karafStandardRepo,
>>>>>> "scr"));
>>>>>>
>>>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>>>> I rememeber that also surefire plugin version has a rule in this
>>>>>> problem.
>>>>>> So I changed my poms as following:
>>>>>>
>>>>>> PARENT-POM
>>>>>>
>>>>>>
>>>>>>     <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>>>                                   <pluginManagement>
>>>>>> <plugins>
>>>>>> <plugin>
>>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>>> <version>${surefire.plugin.version}</version>
>>>>>> <configuration>
>>>>>> <excludes>
>>>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>>>> </excludes>
>>>>>> </configuration>
>>>>>> </plugin>
>>>>>> </plugins>
>>>>>> </pluginManagement>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ITEST-PROJECT-POM
>>>>>>
>>>>>>                            <plugin>
>>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>>> <configuration>
>>>>>> <forkCount>1</forkCount>
>>>>>> <reuseForks>false</reuseForks>
>>>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>>>> <argLine>-Xmx512m</argLine>
>>>>>> <excludes>
>>>>>> </excludes>
>>>>>> <systemPropertyVariables>
>>>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>>>> <karafVersion>${karaf.version}</karafVersion>
>>>>>> </systemPropertyVariables>
>>>>>> </configuration>
>>>>>> </plugin>
>>>>>>
>>>>>>
>>>>>> I hope this can help you.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Giuseppe
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>
>>>>>> Hi Giuseppe,
>>>>>>
>>>>>>>
>>>>>>> not sure I follow you. You mean you change the itest on your local
>>>>>>> copy ?
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>>
>>>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>>>
>>>>>>> Hi JB
>>>>>>>
>>>>>>>> If you remember i had the same problem.
>>>>>>>> After several week and several investigativo, i discovered some
>>>>>>>> difference
>>>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
>>>>>>>> Now
>>>>>>>> It
>>>>>>>> seems solved.
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Giuseppe
>>>>>>>>
>>>>>>>>
>>>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>>>> scritto:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>>> randomly (only for this itest), the container never came up (pax
>>>>>>>>> exam).
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>>
>>>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>>>
>>>>>>>>> Hi JB
>>>>>>>>>
>>>>>>>>> what type of failure?
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> Giuseppe
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>>>
>>>>>>>>>> Hi guys,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to
>>>>>>>>>>> the
>>>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>>>
>>>>>>>>>>> I will remove this test from master and move it to a dedicated PR
>>>>>>>>>>> to
>>>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>>>> PRs).
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>> JB
>>>>>>>>>>> --
>>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>>>> [hidden email]
>>>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>> [hidden email]
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>
>>>>>>> Jean-Baptiste Onofré
>>>>>>> [hidden email]
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Mikael Åsberg
In reply to this post by Grzegorz Grzybek
I've had problems with Pax Exam and surefire after version 2.18.1 of
surefire. Version 2.18.1 was working fine, but versions after that would
often fail with errors along these lines:
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
ExecutionException The forked VM terminated without properly saying
goodbye. VM crash or System.exit called?
Version 2.20.1 finally fixed the above problem but now there is a 30
second wait after each test, but no crash...so I am still stuck at
2.18.1 for Pax Exam. :(
I've been meaning to report it, but didn't get around to it.



On 2017-11-27 08:28, Grzegorz Grzybek wrote:

> Hello
>
> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
> I'd love to investigate the exact cause, but didn't have time yet...
> The surefire/failsafe issue is
> https://issues.apache.org/jira/browse/SUREFIRE-1374
>
> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>
> regards
> Grzegorz Grzybek
>
> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
>> other itest.
>>
>> I will exclude the MavenTest for now, and investigate.
>>
>> Thanks anyway !
>>
>> Regards
>> JB
>>
>>
>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>
>>> Hi JB
>>> although the tests worked on my PC, very often they went wrong on the
>>> jenkins machine.
>>> I did several experiments to find the problem, but it was very difficult
>>> to
>>> understand it.
>>> What I understood is that for some reason the container is too slow to
>>> come
>>> up and the timeout of pax expired before. Why? I don't know.
>>> At the end, I clone the activemq project on the jenkins machine, I start a
>>> build and it works. So I did a diff between activemq itest configuration
>>> and my itest configuration. The result was that I removed some
>>> initialization from my itest:
>>>
>>>           customOptions.add(junitBundles());
>>>           customOptions.add(KarafDistributionOption
>>>               .editConfigurationFilePut("etc/org.apache.karaf.features.cf
>>> g",
>>> "featuresBoot",
>>>                                         "(aries-blueprint, bundle, config,
>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>
>>> then also:
>>>
>>>          MavenUrlReference karafStandardRepo =
>>> maven().groupId("org.apache.karaf.features")
>>>
>>> .artifactId("standard").classifier("features").type("xml").
>>> versionAsInProject();
>>>
>>>    customOptions.add(KarafDistributionOption.features(karafStandardRepo,
>>> "scr"));
>>>
>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>> I rememeber that also surefire plugin version has a rule in this problem.
>>> So I changed my poms as following:
>>>
>>> PARENT-POM
>>>
>>>
>>>    <surefire.plugin.version>2.16</surefire.plugin.version>
>>>                                  <pluginManagement>
>>> <plugins>
>>> <plugin>
>>> <artifactId>maven-surefire-plugin</artifactId>
>>> <version>${surefire.plugin.version}</version>
>>> <configuration>
>>> <excludes>
>>> <exclude>**/*AcceptanceTest.java</exclude>
>>> </excludes>
>>> </configuration>
>>> </plugin>
>>> </plugins>
>>> </pluginManagement>
>>>
>>>
>>>
>>> ITEST-PROJECT-POM
>>>
>>>                           <plugin>
>>> <artifactId>maven-surefire-plugin</artifactId>
>>> <configuration>
>>> <forkCount>1</forkCount>
>>> <reuseForks>false</reuseForks>
>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>> <argLine>-Xmx512m</argLine>
>>> <excludes>
>>> </excludes>
>>> <systemPropertyVariables>
>>> <activemqVersion>${activemq.version}</activemqVersion>
>>> <karafVersion>${karaf.version}</karafVersion>
>>> </systemPropertyVariables>
>>> </configuration>
>>> </plugin>
>>>
>>>
>>> I hope this can help you.
>>>
>>>
>>> Regards
>>> Giuseppe
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>
>>> Hi Giuseppe,
>>>>
>>>> not sure I follow you. You mean you change the itest on your local copy ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>
>>>> Hi JB
>>>>> If you remember i had the same problem.
>>>>> After several week and several investigativo, i discovered some
>>>>> difference
>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now
>>>>> It
>>>>> seems solved.
>>>>>
>>>>>
>>>>> Regards
>>>>> Giuseppe
>>>>>
>>>>>
>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>> scritto:
>>>>>
>>>>> Hi,
>>>>>
>>>>>>
>>>>>> randomly (only for this itest), the container never came up (pax exam).
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>
>>>>>> Hi JB
>>>>>>
>>>>>>> what type of failure?
>>>>>>>
>>>>>>> Regards
>>>>>>> Giuseppe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>
>>>>>>> Hi guys,
>>>>>>>
>>>>>>>
>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>
>>>>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>> PRs).
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>> --
>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> [hidden email]
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>
>>>>>> Jean-Baptiste Onofré
>>>>>> [hidden email]
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> [hidden email]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>


Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
Hi Mikael,

that's not the same issue here.

We updated to surefire 2.20.1 (2.20.0 didn't work).

Regards
JB

On 11/28/2017 11:10 PM, Mikael Åsberg wrote:

> I've had problems with Pax Exam and surefire after version 2.18.1 of surefire.
> Version 2.18.1 was working fine, but versions after that would often fail with
> errors along these lines:
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> ExecutionException The forked VM terminated without properly saying goodbye. VM
> crash or System.exit called?
> Version 2.20.1 finally fixed the above problem but now there is a 30 second wait
> after each test, but no crash...so I am still stuck at 2.18.1 for Pax Exam. :(
> I've been meaning to report it, but didn't get around to it.
>
>
>
> On 2017-11-27 08:28, Grzegorz Grzybek wrote:
>> Hello
>>
>> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
>> I'd love to investigate the exact cause, but didn't have time yet...
>> The surefire/failsafe issue is
>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>
>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>
>> regards
>> Grzegorz Grzybek
>>
>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>
>>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
>>> other itest.
>>>
>>> I will exclude the MavenTest for now, and investigate.
>>>
>>> Thanks anyway !
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>
>>>> Hi JB
>>>> although the tests worked on my PC, very often they went wrong on the
>>>> jenkins machine.
>>>> I did several experiments to find the problem, but it was very difficult
>>>> to
>>>> understand it.
>>>> What I understood is that for some reason the container is too slow to
>>>> come
>>>> up and the timeout of pax expired before. Why? I don't know.
>>>> At the end, I clone the activemq project on the jenkins machine, I start a
>>>> build and it works. So I did a diff between activemq itest configuration
>>>> and my itest configuration. The result was that I removed some
>>>> initialization from my itest:
>>>>
>>>>           customOptions.add(junitBundles());
>>>>           customOptions.add(KarafDistributionOption
>>>>               .editConfigurationFilePut("etc/org.apache.karaf.features.cf
>>>> g",
>>>> "featuresBoot",
>>>>                                         "(aries-blueprint, bundle, config,
>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>
>>>> then also:
>>>>
>>>>          MavenUrlReference karafStandardRepo =
>>>> maven().groupId("org.apache.karaf.features")
>>>>
>>>> .artifactId("standard").classifier("features").type("xml").
>>>> versionAsInProject();
>>>>
>>>>    customOptions.add(KarafDistributionOption.features(karafStandardRepo,
>>>> "scr"));
>>>>
>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>> I rememeber that also surefire plugin version has a rule in this problem.
>>>> So I changed my poms as following:
>>>>
>>>> PARENT-POM
>>>>
>>>>
>>>>    <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>                                  <pluginManagement>
>>>> <plugins>
>>>> <plugin>
>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>> <version>${surefire.plugin.version}</version>
>>>> <configuration>
>>>> <excludes>
>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>> </excludes>
>>>> </configuration>
>>>> </plugin>
>>>> </plugins>
>>>> </pluginManagement>
>>>>
>>>>
>>>>
>>>> ITEST-PROJECT-POM
>>>>
>>>>                           <plugin>
>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>> <configuration>
>>>> <forkCount>1</forkCount>
>>>> <reuseForks>false</reuseForks>
>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>> <argLine>-Xmx512m</argLine>
>>>> <excludes>
>>>> </excludes>
>>>> <systemPropertyVariables>
>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>> <karafVersion>${karaf.version}</karafVersion>
>>>> </systemPropertyVariables>
>>>> </configuration>
>>>> </plugin>
>>>>
>>>>
>>>> I hope this can help you.
>>>>
>>>>
>>>> Regards
>>>> Giuseppe
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>
>>>> Hi Giuseppe,
>>>>>
>>>>> not sure I follow you. You mean you change the itest on your local copy ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>
>>>>> Hi JB
>>>>>> If you remember i had the same problem.
>>>>>> After several week and several investigativo, i discovered some
>>>>>> difference
>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup. Now
>>>>>> It
>>>>>> seems solved.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Giuseppe
>>>>>>
>>>>>>
>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>> scritto:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>>
>>>>>>> randomly (only for this itest), the container never came up (pax exam).
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>
>>>>>>> Hi JB
>>>>>>>
>>>>>>>> what type of failure?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Giuseppe
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>>
>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>
>>>>>>>>> I will remove this test from master and move it to a dedicated PR to
>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>> PRs).
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>> --
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>> [hidden email]
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>
>>>>>>> Jean-Baptiste Onofré
>>>>>>> [hidden email]
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>
>>> --
>>> Jean-Baptiste Onofré
>>> [hidden email]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Grzegorz Grzybek
In reply to this post by Mikael Åsberg
@Mikael - that's what I observed too - 2.20.1 had this (intermittent) 30
seconds timeout after test finishes.

I don't have time (before Code Europe conf.) to check what's the problem
now, but I won't just leave it unexplained...

best regards
Grzegorz Grzybek

2017-11-28 23:10 GMT+01:00 Mikael Åsberg <[hidden email]>:

> I've had problems with Pax Exam and surefire after version 2.18.1 of
> surefire. Version 2.18.1 was working fine, but versions after that would
> often fail with errors along these lines:
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> Version 2.20.1 finally fixed the above problem but now there is a 30
> second wait after each test, but no crash...so I am still stuck at 2.18.1
> for Pax Exam. :(
> I've been meaning to report it, but didn't get around to it.
>
>
>
>
> On 2017-11-27 08:28, Grzegorz Grzybek wrote:
>
>> Hello
>>
>> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
>> I'd love to investigate the exact cause, but didn't have time yet...
>> The surefire/failsafe issue is
>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>
>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>
>> regards
>> Grzegorz Grzybek
>>
>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>
>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
>>> other itest.
>>>
>>> I will exclude the MavenTest for now, and investigate.
>>>
>>> Thanks anyway !
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>
>>> Hi JB
>>>> although the tests worked on my PC, very often they went wrong on the
>>>> jenkins machine.
>>>> I did several experiments to find the problem, but it was very difficult
>>>> to
>>>> understand it.
>>>> What I understood is that for some reason the container is too slow to
>>>> come
>>>> up and the timeout of pax expired before. Why? I don't know.
>>>> At the end, I clone the activemq project on the jenkins machine, I
>>>> start a
>>>> build and it works. So I did a diff between activemq itest configuration
>>>> and my itest configuration. The result was that I removed some
>>>> initialization from my itest:
>>>>
>>>>           customOptions.add(junitBundles());
>>>>           customOptions.add(KarafDistributionOption
>>>>               .editConfigurationFilePut("etc/
>>>> org.apache.karaf.features.cf
>>>> g",
>>>> "featuresBoot",
>>>>                                         "(aries-blueprint, bundle,
>>>> config,
>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>
>>>> then also:
>>>>
>>>>          MavenUrlReference karafStandardRepo =
>>>> maven().groupId("org.apache.karaf.features")
>>>>
>>>> .artifactId("standard").classifier("features").type("xml").
>>>> versionAsInProject();
>>>>
>>>>    customOptions.add(KarafDistributionOption.features(
>>>> karafStandardRepo,
>>>> "scr"));
>>>>
>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>> I rememeber that also surefire plugin version has a rule in this
>>>> problem.
>>>> So I changed my poms as following:
>>>>
>>>> PARENT-POM
>>>>
>>>>
>>>>    <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>                                  <pluginManagement>
>>>> <plugins>
>>>> <plugin>
>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>> <version>${surefire.plugin.version}</version>
>>>> <configuration>
>>>> <excludes>
>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>> </excludes>
>>>> </configuration>
>>>> </plugin>
>>>> </plugins>
>>>> </pluginManagement>
>>>>
>>>>
>>>>
>>>> ITEST-PROJECT-POM
>>>>
>>>>                           <plugin>
>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>> <configuration>
>>>> <forkCount>1</forkCount>
>>>> <reuseForks>false</reuseForks>
>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>> <argLine>-Xmx512m</argLine>
>>>> <excludes>
>>>> </excludes>
>>>> <systemPropertyVariables>
>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>> <karafVersion>${karaf.version}</karafVersion>
>>>> </systemPropertyVariables>
>>>> </configuration>
>>>> </plugin>
>>>>
>>>>
>>>> I hope this can help you.
>>>>
>>>>
>>>> Regards
>>>> Giuseppe
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>
>>>> Hi Giuseppe,
>>>>
>>>>>
>>>>> not sure I follow you. You mean you change the itest on your local
>>>>> copy ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>
>>>>> Hi JB
>>>>>
>>>>>> If you remember i had the same problem.
>>>>>> After several week and several investigativo, i discovered some
>>>>>> difference
>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
>>>>>> Now
>>>>>> It
>>>>>> seems solved.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Giuseppe
>>>>>>
>>>>>>
>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>> scritto:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>>> randomly (only for this itest), the container never came up (pax
>>>>>>> exam).
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>
>>>>>>> Hi JB
>>>>>>>
>>>>>>> what type of failure?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Giuseppe
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>>
>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>
>>>>>>>>> I will remove this test from master and move it to a dedicated PR
>>>>>>>>> to
>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>> PRs).
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>> --
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>> [hidden email]
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>
>>>>>>>> Jean-Baptiste Onofré
>>>>>>> [hidden email]
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> [hidden email]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

jbonofre
I excluded MavenTest and now the build is way more stable on Jenkins.

I will investigate.

Regards
JB

On 11/29/2017 06:16 AM, Grzegorz Grzybek wrote:

> @Mikael - that's what I observed too - 2.20.1 had this (intermittent) 30
> seconds timeout after test finishes.
>
> I don't have time (before Code Europe conf.) to check what's the problem
> now, but I won't just leave it unexplained...
>
> best regards
> Grzegorz Grzybek
>
> 2017-11-28 23:10 GMT+01:00 Mikael Åsberg <[hidden email]>:
>
>> I've had problems with Pax Exam and surefire after version 2.18.1 of
>> surefire. Version 2.18.1 was working fine, but versions after that would
>> often fail with errors along these lines:
>> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
>> ExecutionException The forked VM terminated without properly saying
>> goodbye. VM crash or System.exit called?
>> Version 2.20.1 finally fixed the above problem but now there is a 30
>> second wait after each test, but no crash...so I am still stuck at 2.18.1
>> for Pax Exam. :(
>> I've been meaning to report it, but didn't get around to it.
>>
>>
>>
>>
>> On 2017-11-27 08:28, Grzegorz Grzybek wrote:
>>
>>> Hello
>>>
>>> I found that maven-surefire-plugin 2.20+ has some problems with pax-exam.
>>> I'd love to investigate the exact cause, but didn't have time yet...
>>> The surefire/failsafe issue is
>>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>>
>>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>>
>>> regards
>>> Grzegorz Grzybek
>>>
>>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>
>>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch of
>>>> other itest.
>>>>
>>>> I will exclude the MavenTest for now, and investigate.
>>>>
>>>> Thanks anyway !
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>>
>>>> Hi JB
>>>>> although the tests worked on my PC, very often they went wrong on the
>>>>> jenkins machine.
>>>>> I did several experiments to find the problem, but it was very difficult
>>>>> to
>>>>> understand it.
>>>>> What I understood is that for some reason the container is too slow to
>>>>> come
>>>>> up and the timeout of pax expired before. Why? I don't know.
>>>>> At the end, I clone the activemq project on the jenkins machine, I
>>>>> start a
>>>>> build and it works. So I did a diff between activemq itest configuration
>>>>> and my itest configuration. The result was that I removed some
>>>>> initialization from my itest:
>>>>>
>>>>>            customOptions.add(junitBundles());
>>>>>            customOptions.add(KarafDistributionOption
>>>>>                .editConfigurationFilePut("etc/
>>>>> org.apache.karaf.features.cf
>>>>> g",
>>>>> "featuresBoot",
>>>>>                                          "(aries-blueprint, bundle,
>>>>> config,
>>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>>
>>>>> then also:
>>>>>
>>>>>           MavenUrlReference karafStandardRepo =
>>>>> maven().groupId("org.apache.karaf.features")
>>>>>
>>>>> .artifactId("standard").classifier("features").type("xml").
>>>>> versionAsInProject();
>>>>>
>>>>>     customOptions.add(KarafDistributionOption.features(
>>>>> karafStandardRepo,
>>>>> "scr"));
>>>>>
>>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>>> I rememeber that also surefire plugin version has a rule in this
>>>>> problem.
>>>>> So I changed my poms as following:
>>>>>
>>>>> PARENT-POM
>>>>>
>>>>>
>>>>>     <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>>                                   <pluginManagement>
>>>>> <plugins>
>>>>> <plugin>
>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>> <version>${surefire.plugin.version}</version>
>>>>> <configuration>
>>>>> <excludes>
>>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>>> </excludes>
>>>>> </configuration>
>>>>> </plugin>
>>>>> </plugins>
>>>>> </pluginManagement>
>>>>>
>>>>>
>>>>>
>>>>> ITEST-PROJECT-POM
>>>>>
>>>>>                            <plugin>
>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>> <configuration>
>>>>> <forkCount>1</forkCount>
>>>>> <reuseForks>false</reuseForks>
>>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>>> <argLine>-Xmx512m</argLine>
>>>>> <excludes>
>>>>> </excludes>
>>>>> <systemPropertyVariables>
>>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>>> <karafVersion>${karaf.version}</karafVersion>
>>>>> </systemPropertyVariables>
>>>>> </configuration>
>>>>> </plugin>
>>>>>
>>>>>
>>>>> I hope this can help you.
>>>>>
>>>>>
>>>>> Regards
>>>>> Giuseppe
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>
>>>>> Hi Giuseppe,
>>>>>
>>>>>>
>>>>>> not sure I follow you. You mean you change the itest on your local
>>>>>> copy ?
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>>
>>>>>> Hi JB
>>>>>>
>>>>>>> If you remember i had the same problem.
>>>>>>> After several week and several investigativo, i discovered some
>>>>>>> difference
>>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
>>>>>>> Now
>>>>>>> It
>>>>>>> seems solved.
>>>>>>>
>>>>>>>
>>>>>>> Regards
>>>>>>> Giuseppe
>>>>>>>
>>>>>>>
>>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>>> scritto:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>> randomly (only for this itest), the container never came up (pax
>>>>>>>> exam).
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>>
>>>>>>>> Hi JB
>>>>>>>>
>>>>>>>> what type of failure?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> Giuseppe
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>>
>>>>>>>>> Hi guys,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to the
>>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>>
>>>>>>>>>> I will remove this test from master and move it to a dedicated PR
>>>>>>>>>> to
>>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>>> PRs).
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> JB
>>>>>>>>>> --
>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>>> [hidden email]
>>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> [hidden email]
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>
>>>>>> Jean-Baptiste Onofré
>>>>>> [hidden email]
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> [hidden email]
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>>
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

Grzegorz Grzybek
Thanks!

I'll have a look too - but not this week. @Ignoring it is good idea for now
- timeouts proved to be working well for long time now.

regards
Grzegorz Grzybek

2017-11-29 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:

> I excluded MavenTest and now the build is way more stable on Jenkins.
>
> I will investigate.
>
> Regards
> JB
>
>
> On 11/29/2017 06:16 AM, Grzegorz Grzybek wrote:
>
>> @Mikael - that's what I observed too - 2.20.1 had this (intermittent) 30
>> seconds timeout after test finishes.
>>
>> I don't have time (before Code Europe conf.) to check what's the problem
>> now, but I won't just leave it unexplained...
>>
>> best regards
>> Grzegorz Grzybek
>>
>> 2017-11-28 23:10 GMT+01:00 Mikael Åsberg <[hidden email]>:
>>
>> I've had problems with Pax Exam and surefire after version 2.18.1 of
>>> surefire. Version 2.18.1 was working fine, but versions after that would
>>> often fail with errors along these lines:
>>> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
>>> ExecutionException The forked VM terminated without properly saying
>>> goodbye. VM crash or System.exit called?
>>> Version 2.20.1 finally fixed the above problem but now there is a 30
>>> second wait after each test, but no crash...so I am still stuck at 2.18.1
>>> for Pax Exam. :(
>>> I've been meaning to report it, but didn't get around to it.
>>>
>>>
>>>
>>>
>>> On 2017-11-27 08:28, Grzegorz Grzybek wrote:
>>>
>>> Hello
>>>>
>>>> I found that maven-surefire-plugin 2.20+ has some problems with
>>>> pax-exam.
>>>> I'd love to investigate the exact cause, but didn't have time yet...
>>>> The surefire/failsafe issue is
>>>> https://issues.apache.org/jira/browse/SUREFIRE-1374
>>>>
>>>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
>>>>
>>>> regards
>>>> Grzegorz Grzybek
>>>>
>>>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>
>>>> Hmm, not sure it's related as we use the same KarafTestSupport in bunch
>>>> of
>>>>
>>>>> other itest.
>>>>>
>>>>> I will exclude the MavenTest for now, and investigate.
>>>>>
>>>>> Thanks anyway !
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
>>>>>
>>>>> Hi JB
>>>>>
>>>>>> although the tests worked on my PC, very often they went wrong on the
>>>>>> jenkins machine.
>>>>>> I did several experiments to find the problem, but it was very
>>>>>> difficult
>>>>>> to
>>>>>> understand it.
>>>>>> What I understood is that for some reason the container is too slow to
>>>>>> come
>>>>>> up and the timeout of pax expired before. Why? I don't know.
>>>>>> At the end, I clone the activemq project on the jenkins machine, I
>>>>>> start a
>>>>>> build and it works. So I did a diff between activemq itest
>>>>>> configuration
>>>>>> and my itest configuration. The result was that I removed some
>>>>>> initialization from my itest:
>>>>>>
>>>>>>            customOptions.add(junitBundles());
>>>>>>            customOptions.add(KarafDistributionOption
>>>>>>                .editConfigurationFilePut("etc/
>>>>>> org.apache.karaf.features.cf
>>>>>> g",
>>>>>> "featuresBoot",
>>>>>>                                          "(aries-blueprint, bundle,
>>>>>> config,
>>>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
>>>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
>>>>>>
>>>>>> then also:
>>>>>>
>>>>>>           MavenUrlReference karafStandardRepo =
>>>>>> maven().groupId("org.apache.karaf.features")
>>>>>>
>>>>>> .artifactId("standard").classifier("features").type("xml").
>>>>>> versionAsInProject();
>>>>>>
>>>>>>     customOptions.add(KarafDistributionOption.features(
>>>>>> karafStandardRepo,
>>>>>> "scr"));
>>>>>>
>>>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
>>>>>> I rememeber that also surefire plugin version has a rule in this
>>>>>> problem.
>>>>>> So I changed my poms as following:
>>>>>>
>>>>>> PARENT-POM
>>>>>>
>>>>>>
>>>>>>     <surefire.plugin.version>2.16</surefire.plugin.version>
>>>>>>                                   <pluginManagement>
>>>>>> <plugins>
>>>>>> <plugin>
>>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>>> <version>${surefire.plugin.version}</version>
>>>>>> <configuration>
>>>>>> <excludes>
>>>>>> <exclude>**/*AcceptanceTest.java</exclude>
>>>>>> </excludes>
>>>>>> </configuration>
>>>>>> </plugin>
>>>>>> </plugins>
>>>>>> </pluginManagement>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ITEST-PROJECT-POM
>>>>>>
>>>>>>                            <plugin>
>>>>>> <artifactId>maven-surefire-plugin</artifactId>
>>>>>> <configuration>
>>>>>> <forkCount>1</forkCount>
>>>>>> <reuseForks>false</reuseForks>
>>>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
>>>>>> <argLine>-Xmx512m</argLine>
>>>>>> <excludes>
>>>>>> </excludes>
>>>>>> <systemPropertyVariables>
>>>>>> <activemqVersion>${activemq.version}</activemqVersion>
>>>>>> <karafVersion>${karaf.version}</karafVersion>
>>>>>> </systemPropertyVariables>
>>>>>> </configuration>
>>>>>> </plugin>
>>>>>>
>>>>>>
>>>>>> I hope this can help you.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Giuseppe
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>
>>>>>> Hi Giuseppe,
>>>>>>
>>>>>>
>>>>>>> not sure I follow you. You mean you change the itest on your local
>>>>>>> copy ?
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>>
>>>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
>>>>>>>
>>>>>>> Hi JB
>>>>>>>
>>>>>>> If you remember i had the same problem.
>>>>>>>> After several week and several investigativo, i discovered some
>>>>>>>> difference
>>>>>>>> beteeen my itest and activemq itest. So i changed my itest sturtup.
>>>>>>>> Now
>>>>>>>> It
>>>>>>>> seems solved.
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Giuseppe
>>>>>>>>
>>>>>>>>
>>>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
>>>>>>>> scritto:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>> randomly (only for this itest), the container never came up (pax
>>>>>>>>> exam).
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>>
>>>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
>>>>>>>>>
>>>>>>>>> Hi JB
>>>>>>>>>
>>>>>>>>> what type of failure?
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> Giuseppe
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>>>>>>>>>>
>>>>>>>>>> Hi guys,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to
>>>>>>>>>> the
>>>>>>>>>>
>>>>>>>>>>> MavenTest which randomly fails (but often).
>>>>>>>>>>>
>>>>>>>>>>> I will remove this test from master and move it to a dedicated PR
>>>>>>>>>>> to
>>>>>>>>>>> investigate (but at least it won't impact our nightly builds and
>>>>>>>>>>> PRs).
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>> JB
>>>>>>>>>>> --
>>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>>>> [hidden email]
>>>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>>>
>>>>>>>>> [hidden email]
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>
>>>>>>>> Jean-Baptiste Onofré
>>>>>>> [hidden email]
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>
>>>>> Jean-Baptiste Onofré
>>>>> [hidden email]
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [UPDATE] MavenTest itest fails randomly but often

ggerla
Just to be sure... could you try with surefire 2.16.
Because during my investigation I had problems with both 2.18.1 and 2.20.1
(that is better than 2.20.0 but not problem free).


Regards
Giuseppe



2017-11-29 7:54 GMT+01:00 Grzegorz Grzybek <[hidden email]>:

> Thanks!
>
> I'll have a look too - but not this week. @Ignoring it is good idea for now
> - timeouts proved to be working well for long time now.
>
> regards
> Grzegorz Grzybek
>
> 2017-11-29 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
>
> > I excluded MavenTest and now the build is way more stable on Jenkins.
> >
> > I will investigate.
> >
> > Regards
> > JB
> >
> >
> > On 11/29/2017 06:16 AM, Grzegorz Grzybek wrote:
> >
> >> @Mikael - that's what I observed too - 2.20.1 had this (intermittent) 30
> >> seconds timeout after test finishes.
> >>
> >> I don't have time (before Code Europe conf.) to check what's the problem
> >> now, but I won't just leave it unexplained...
> >>
> >> best regards
> >> Grzegorz Grzybek
> >>
> >> 2017-11-28 23:10 GMT+01:00 Mikael Åsberg <[hidden email]>:
> >>
> >> I've had problems with Pax Exam and surefire after version 2.18.1 of
> >>> surefire. Version 2.18.1 was working fine, but versions after that
> would
> >>> often fail with errors along these lines:
> >>> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> >>> ExecutionException The forked VM terminated without properly saying
> >>> goodbye. VM crash or System.exit called?
> >>> Version 2.20.1 finally fixed the above problem but now there is a 30
> >>> second wait after each test, but no crash...so I am still stuck at
> 2.18.1
> >>> for Pax Exam. :(
> >>> I've been meaning to report it, but didn't get around to it.
> >>>
> >>>
> >>>
> >>>
> >>> On 2017-11-27 08:28, Grzegorz Grzybek wrote:
> >>>
> >>> Hello
> >>>>
> >>>> I found that maven-surefire-plugin 2.20+ has some problems with
> >>>> pax-exam.
> >>>> I'd love to investigate the exact cause, but didn't have time yet...
> >>>> The surefire/failsafe issue is
> >>>> https://issues.apache.org/jira/browse/SUREFIRE-1374
> >>>>
> >>>> And in my (jboss fuse) integration tests I stayed with 2.19.x.
> >>>>
> >>>> regards
> >>>> Grzegorz Grzybek
> >>>>
> >>>> 2017-11-27 7:32 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> >>>>
> >>>> Hmm, not sure it's related as we use the same KarafTestSupport in
> bunch
> >>>> of
> >>>>
> >>>>> other itest.
> >>>>>
> >>>>> I will exclude the MavenTest for now, and investigate.
> >>>>>
> >>>>> Thanks anyway !
> >>>>>
> >>>>> Regards
> >>>>> JB
> >>>>>
> >>>>>
> >>>>> On 11/26/2017 09:50 AM, Giuseppe Gerla wrote:
> >>>>>
> >>>>> Hi JB
> >>>>>
> >>>>>> although the tests worked on my PC, very often they went wrong on
> the
> >>>>>> jenkins machine.
> >>>>>> I did several experiments to find the problem, but it was very
> >>>>>> difficult
> >>>>>> to
> >>>>>> understand it.
> >>>>>> What I understood is that for some reason the container is too slow
> to
> >>>>>> come
> >>>>>> up and the timeout of pax expired before. Why? I don't know.
> >>>>>> At the end, I clone the activemq project on the jenkins machine, I
> >>>>>> start a
> >>>>>> build and it works. So I did a diff between activemq itest
> >>>>>> configuration
> >>>>>> and my itest configuration. The result was that I removed some
> >>>>>> initialization from my itest:
> >>>>>>
> >>>>>>            customOptions.add(junitBundles());
> >>>>>>            customOptions.add(KarafDistributionOption
> >>>>>>                .editConfigurationFilePut("etc/
> >>>>>> org.apache.karaf.features.cf
> >>>>>> g",
> >>>>>> "featuresBoot",
> >>>>>>                                          "(aries-blueprint, bundle,
> >>>>>> config,
> >>>>>> deployer, diagnostic, feature, instance, jaas, kar, log, management,
> >>>>>> package, service, shell, shell-compat, ssh, system, wrap)"));
> >>>>>>
> >>>>>> then also:
> >>>>>>
> >>>>>>           MavenUrlReference karafStandardRepo =
> >>>>>> maven().groupId("org.apache.karaf.features")
> >>>>>>
> >>>>>> .artifactId("standard").classifier("features").type("xml").
> >>>>>> versionAsInProject();
> >>>>>>
> >>>>>>     customOptions.add(KarafDistributionOption.features(
> >>>>>> karafStandardRepo,
> >>>>>> "scr"));
> >>>>>>
> >>>>>> and I replaced "activemq-broker-noweb" feature with "activemq" one.
> >>>>>> I rememeber that also surefire plugin version has a rule in this
> >>>>>> problem.
> >>>>>> So I changed my poms as following:
> >>>>>>
> >>>>>> PARENT-POM
> >>>>>>
> >>>>>>
> >>>>>>     <surefire.plugin.version>2.16</surefire.plugin.version>
> >>>>>>                                   <pluginManagement>
> >>>>>> <plugins>
> >>>>>> <plugin>
> >>>>>> <artifactId>maven-surefire-plugin</artifactId>
> >>>>>> <version>${surefire.plugin.version}</version>
> >>>>>> <configuration>
> >>>>>> <excludes>
> >>>>>> <exclude>**/*AcceptanceTest.java</exclude>
> >>>>>> </excludes>
> >>>>>> </configuration>
> >>>>>> </plugin>
> >>>>>> </plugins>
> >>>>>> </pluginManagement>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ITEST-PROJECT-POM
> >>>>>>
> >>>>>>                            <plugin>
> >>>>>> <artifactId>maven-surefire-plugin</artifactId>
> >>>>>> <configuration>
> >>>>>> <forkCount>1</forkCount>
> >>>>>> <reuseForks>false</reuseForks>
> >>>>>> <redirectTestOutputToFile>true</redirectTestOutputToFile>
> >>>>>> <argLine>-Xmx512m</argLine>
> >>>>>> <excludes>
> >>>>>> </excludes>
> >>>>>> <systemPropertyVariables>
> >>>>>> <activemqVersion>${activemq.version}</activemqVersion>
> >>>>>> <karafVersion>${karaf.version}</karafVersion>
> >>>>>> </systemPropertyVariables>
> >>>>>> </configuration>
> >>>>>> </plugin>
> >>>>>>
> >>>>>>
> >>>>>> I hope this can help you.
> >>>>>>
> >>>>>>
> >>>>>> Regards
> >>>>>> Giuseppe
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré <[hidden email]>:
> >>>>>>
> >>>>>> Hi Giuseppe,
> >>>>>>
> >>>>>>
> >>>>>>> not sure I follow you. You mean you change the itest on your local
> >>>>>>> copy ?
> >>>>>>>
> >>>>>>> Regards
> >>>>>>> JB
> >>>>>>>
> >>>>>>>
> >>>>>>> On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
> >>>>>>>
> >>>>>>> Hi JB
> >>>>>>>
> >>>>>>> If you remember i had the same problem.
> >>>>>>>> After several week and several investigativo, i discovered some
> >>>>>>>> difference
> >>>>>>>> beteeen my itest and activemq itest. So i changed my itest
> sturtup.
> >>>>>>>> Now
> >>>>>>>> It
> >>>>>>>> seems solved.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Regards
> >>>>>>>> Giuseppe
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" <[hidden email]> ha
> >>>>>>>> scritto:
> >>>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> randomly (only for this itest), the container never came up (pax
> >>>>>>>>> exam).
> >>>>>>>>>
> >>>>>>>>> Regards
> >>>>>>>>> JB
> >>>>>>>>>
> >>>>>>>>> On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
> >>>>>>>>>
> >>>>>>>>> Hi JB
> >>>>>>>>>
> >>>>>>>>> what type of failure?
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Regards
> >>>>>>>>>> Giuseppe
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré <[hidden email]
> >:
> >>>>>>>>>>
> >>>>>>>>>> Hi guys,
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Our Jenkins jobs are not very stable (both master and PR) due to
> >>>>>>>>>> the
> >>>>>>>>>>
> >>>>>>>>>>> MavenTest which randomly fails (but often).
> >>>>>>>>>>>
> >>>>>>>>>>> I will remove this test from master and move it to a dedicated
> PR
> >>>>>>>>>>> to
> >>>>>>>>>>> investigate (but at least it won't impact our nightly builds
> and
> >>>>>>>>>>> PRs).
> >>>>>>>>>>>
> >>>>>>>>>>> Regards
> >>>>>>>>>>> JB
> >>>>>>>>>>> --
> >>>>>>>>>>> Jean-Baptiste Onofré
> >>>>>>>>>>> [hidden email]
> >>>>>>>>>>> http://blog.nanthrax.net
> >>>>>>>>>>> Talend - http://www.talend.com
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>> Jean-Baptiste Onofré
> >>>>>>>>>>
> >>>>>>>>> [hidden email]
> >>>>>>>>> http://blog.nanthrax.net
> >>>>>>>>> Talend - http://www.talend.com
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Jean-Baptiste Onofré
> >>>>>>> [hidden email]
> >>>>>>> http://blog.nanthrax.net
> >>>>>>> Talend - http://www.talend.com
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>
> >>>>> Jean-Baptiste Onofré
> >>>>> [hidden email]
> >>>>> http://blog.nanthrax.net
> >>>>> Talend - http://www.talend.com
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> > --
> > Jean-Baptiste Onofré
> > [hidden email]
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
12