Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 23FFC200D4B for ; Mon, 27 Nov 2017 09:18:47 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 227BE160C02; Mon, 27 Nov 2017 08:18:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 42AAF160C13 for ; Mon, 27 Nov 2017 09:18:46 +0100 (CET) Received: (qmail 75463 invoked by uid 500); 27 Nov 2017 08:18:45 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Received: (qmail 75381 invoked by uid 99); 27 Nov 2017 08:18:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2017 08:18:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 530D81A0E19 for ; Mon, 27 Nov 2017 08:18:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.28 X-Spam-Level: X-Spam-Status: No, score=0.28 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Q0PwO-HzPTQ7 for ; Mon, 27 Nov 2017 08:18:42 +0000 (UTC) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9BAC15F286 for ; Mon, 27 Nov 2017 08:18:41 +0000 (UTC) X-Originating-IP: 82.238.224.4 Received: from [192.168.134.109] (bre91-1-82-238-224-4.fbx.proxad.net [82.238.224.4]) (Authenticated sender: jb@nanthrax.net) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id A5FBEC5A63 for ; Mon, 27 Nov 2017 09:18:34 +0100 (CET) Subject: Re: [UPDATE] MavenTest itest fails randomly but often To: dev@karaf.apache.org References: <94c2e86d-222b-e0b1-c6c1-5a4b5da9d05d@nanthrax.net> <5c544a8b-229a-623d-25ec-be9b7a8bb5b2@nanthrax.net> <8d5dc1e0-9126-ec0b-4f2b-a81f29169482@nanthrax.net> From: =?UTF-8?Q?Jean-Baptiste_Onofr=c3=a9?= Message-ID: <507662c9-bfe3-07ba-b60a-f4f5a42d3d5a@nanthrax.net> Date: Mon, 27 Nov 2017 09:18:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit archived-at: Mon, 27 Nov 2017 08:18:47 -0000 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é : > >> 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 >>> >>> >>> 2.16 >>> >>> >>> >>> maven-surefire-plugin >>> ${surefire.plugin.version} >>> >>> >>> **/*AcceptanceTest.java >>> >>> >>> >>> >>> >>> >>> >>> >>> ITEST-PROJECT-POM >>> >>> >>> maven-surefire-plugin >>> >>> 1 >>> false >>> true >>> -Xmx512m >>> >>> >>> >>> ${activemq.version} >>> ${karaf.version} >>> >>> >>> >>> >>> >>> I hope this can help you. >>> >>> >>> Regards >>> Giuseppe >>> >>> >>> >>> >>> >>> >>> >>> >>> 2017-11-26 7:17 GMT+01:00 Jean-Baptiste Onofré : >>> >>> 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é" 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é : >>>>>>> >>>>>>> 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é >>>>>>>> jbonofre@apache.org >>>>>>>> http://blog.nanthrax.net >>>>>>>> Talend - http://www.talend.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> >>>>>> Jean-Baptiste Onofré >>>>>> jbonofre@apache.org >>>>>> http://blog.nanthrax.net >>>>>> Talend - http://www.talend.com >>>>>> >>>>>> >>>>>> >>>>> -- >>>> Jean-Baptiste Onofré >>>> jbonofre@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >>>> >>>> >>> >> -- >> Jean-Baptiste Onofré >> jbonofre@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> > -- Jean-Baptiste Onofré jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com