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 5E1B0200BBA for ; Fri, 21 Oct 2016 17:31:43 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5CC6D160ADE; Fri, 21 Oct 2016 15:31:43 +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 A3392160AE8 for ; Fri, 21 Oct 2016 17:31:42 +0200 (CEST) Received: (qmail 31852 invoked by uid 500); 21 Oct 2016 15:31:36 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 31830 invoked by uid 99); 21 Oct 2016 15:31:36 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2016 15:31:36 +0000 Received: from v45346.1blu.de (v45346.1blu.de [178.254.23.72]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 430F61A00D9; Fri, 21 Oct 2016 15:31:36 +0000 (UTC) Received: by v45346.1blu.de (Postfix, from userid 1000) id 085D6400011; Fri, 21 Oct 2016 17:31:34 +0200 (CEST) From: Stefan Bodewig To: general@gump.apache.org Cc: POI Developers List Subject: Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed References: <20161020014842.44E89141428@vmgump.apache.org> Date: Fri, 21 Oct 2016 17:31:34 +0200 In-Reply-To: (Dominik Stadler's message of "Thu, 20 Oct 2016 10:27:48 +0200") Message-ID: <87funp67mx.fsf@v45346.1blu.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain archived-at: Fri, 21 Oct 2016 15:31:43 -0000 Hi Dominik On 2016-10-20, Dominik Stadler wrote: > Since some time one of the steps in the POI builds inside Gump is failing, > see below. We think it is related to the 1 hour timeout that is applied by > default. Yes, looks that way. > The step compiles a big number of files, but finishes in a few minutes > usually. Our builds on the Apache Jenkins instance usually take up to 40 > minutes for the complete build which includes a number of additional steps, > so we are not sure why it is taking so long here, maybe the machine is > quite limited on memory/CPU? Yes, vmgump is a pretty limited. We are in the process of replacing it, but it may take a while until we get there. > Is there a simple way to try to increase the timeout for this specific > build? This is not implemented, although most of the infrastructure would be there. In case anybody with some working Python knowledge can spare a bit of time: https://svn.apache.org/repos/asf/gump/live/ holds the code. All builders create an instance of gump.util.process.Cmd and the timeout value could be configured via a constructor arg. For POI it would be enough to add an optional timeout property to gump.core.model.builder.Ant (likely Builder would be the better place) and use that from gump.core.build.Ant.getAntCommand - the builder instance is project.ant. I'm not sure how quick I'd be able to make the changes myself, I'm switching between a couple of tasks (including the new VM for gump) right now. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org