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 938C7200D58 for ; Sun, 17 Dec 2017 13:18:16 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 91B13160C17; Sun, 17 Dec 2017 12:18:16 +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 B033A160BFF for ; Sun, 17 Dec 2017 13:18:15 +0100 (CET) Received: (qmail 5399 invoked by uid 500); 17 Dec 2017 12:18:14 -0000 Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list dev@ofbiz.apache.org Received: (qmail 5388 invoked by uid 99); 17 Dec 2017 12:18:14 -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; Sun, 17 Dec 2017 12:18:14 +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 F0D131A001A for ; Sun, 17 Dec 2017 12:18:13 +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-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id p2TWiJPp2Vu2 for ; Sun, 17 Dec 2017 12:18:11 +0000 (UTC) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.1]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 7E9D75F367 for ; Sun, 17 Dec 2017 12:18:11 +0000 (UTC) Received: from [192.168.1.2] (183.90.14.81.rev.sfr.net [81.14.90.183]) by msfrf2613.sfr.fr (SMTP Server) with ESMTP id 605451C00040E for ; Sun, 17 Dec 2017 13:18:04 +0100 (CET) Received: from [192.168.1.2] (183.90.14.81.rev.sfr.net [81.14.90.183]) (Authenticated sender: jacques.leroux60@sfr.fr) by msfrf2613.sfr.fr (SMTP Server) with ESMTPA for ; Sun, 17 Dec 2017 13:18:03 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=jacques.leroux60@sfr.fr Subject: Re: buildbot failure in on ofbiz-trunk-framework-plugins To: dev@ofbiz.apache.org References: <20171213143624.0BF262201A5@buildbot-vm.apache.org> <8cbf9e84-ab9d-c1aa-261e-254e35961a02@les7arts.com> <345ffb85-168a-9aad-5253-392e5b6f2b7c@les7arts.com> From: Jacques Le Roux Organization: Les Arts Informatiques Message-ID: <322ffd1b-e8c2-b05a-aa54-83d14dd498b9@les7arts.com> Date: Sun, 17 Dec 2017 13:18:04 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: X-sfr-mailing: LEGIT Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB archived-at: Sun, 17 Dec 2017 12:18:16 -0000 Hi Taher, I did not find something specific. The message I try to convey is this is an external random condition, not related to Buildbot or our script but the network+servers context. From time to time (more often since the date I put in the Infra Jira, but I can't see a relation with changes then in our script and it was happening before also) the tests fail and when I manually restart the same build they pass. So for me it's not due to our script, which is only starting the tests, but to another conditions(/s?) on the network+servers context. Note that we use 3 test servers. Note also that it happens that the "svn up"' phase fails. I once asked Gavin and he the told me that in such case I simply have to manually restart the tests... That's when I learnt how to do it and that's what, among other things but mostly, I want to document Thanks to care! Jacques Le 17/12/2017 à 12:37, Taher Alkhateeb a écrit : > Hi Jacques, I still don't understand how you determined that it is > _not_ a buildbot scripting issue? I need that information in order to > isolate the cause of these annoying error messages. I find it unlikely > to be a genuine bug in buildbot and more likely a bug in our scripts. > So perhaps you can share what you found so that I focus my efforts in > the right place? > > On Wed, Dec 13, 2017 at 9:07 PM, Jacques Le Roux > wrote: >> Taher, >> >> Look at >> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins?numbuilds=150 >> >> From time to time, when I find weird that a build fails on Buildbot but not >> locally, I force a build on Buildbot manually (ie redo an existing commit) >> and then it passes >> Eg: >> Dec 05 06:47 >> >> 1817154 success #797 >> >> forced: by IRC user (privmsg): forces manual build after tests >> errors Build successful >> Dec 05 04:16 1817151 failure #796 >> >> The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered >> this build Failed shell_4 >> >> >> Dec 08 19:40 >> >> 1817550 success #805 >> >> The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered >> this build Build successful >> Dec 08 10:14 1817479 success #804 >> >> forced: by IRC user (privmsg): forces manual build after BuilBot >> signaling a failure (OK locally) Build successful >> >> >> Of course you can check there are no OFBiz commits between these forcings. >> Remember we share SVN and Buildbot with other TLPs... >> >> At contratrio, this one was a real issue I wanted to be sure about, see it >> fails 2 times... >> Dec 13 10:23 >> >> 1817994 failure #869 >> >> forced: by IRC user (privmsg): forces manual build to check we >> have a real error with testPerformFind Failed shell_4 >> Dec 13 09:23 1817989 failure #868 >> >> The AnyBranchScheduler scheduler named 'on-ofbiz-framework-commit' triggered >> this build Failed shell_4 >> >> >> You can find the same on >> https://ci.apache.org/builders/ofbiz-trunk-framework?numbuilds=150 >> >> BTW this was a good question and I'll add this info in the infra request. >> >> I tend to forgot about how I do things. I'm really the kind of intuitive >> people. But I can help myself when I need to help others :) >> >> Jacques >> >> >> Le 13/12/2017 à 17:12, Taher Alkhateeb a écrit : >>> How did you determine it's not the buildbot script? >>> >>> On Wed, Dec 13, 2017 at 7:05 PM, Jacques Le Roux >>> wrote: >>>> I fear it's not part of our BuildBot config, so I asked help from infra. >>>> Maybe this can help >>>> >>>> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15394 >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 13/12/2017 à 16:21, Taher Alkhateeb a écrit : >>>>> These error messages are becoming excessive and indicating a faulty >>>>> buildbot implementation. I would like to work on it. Is anyone >>>>> interested in helping me or has background information that might >>>>> help? >>>>> >>>>> On Wed, Dec 13, 2017 at 5:36 PM, wrote: >>>>>> The Buildbot has detected a new failure on builder >>>>>> ofbiz-trunk-framework-plugins while building . Full details are >>>>>> available >>>>>> at: >>>>>> >>>>>> https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/877 >>>>>> >>>>>> Buildbot URL: https://ci.apache.org/ >>>>>> >>>>>> Buildslave for this Build: silvanus_ubuntu >>>>>> >>>>>> Build Reason: The AnyBranchScheduler scheduler named >>>>>> 'on-ofbiz-framework-commit' triggered this build >>>>>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1818020 >>>>>> Blamelist: jleroux >>>>>> >>>>>> BUILD FAILED: failed shell_4 >>>>>> >>>>>> Sincerely, >>>>>> -The Buildbot >>>>>> >>>>>> >>>>>>