Return-Path: X-Original-To: apmail-gump-general-archive@www.apache.org Delivered-To: apmail-gump-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DD5619D2C for ; Thu, 27 Dec 2012 06:18:56 +0000 (UTC) Received: (qmail 38870 invoked by uid 500); 27 Dec 2012 06:18:56 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 38675 invoked by uid 500); 27 Dec 2012 06:18:50 -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 38622 invoked by uid 99); 27 Dec 2012 06:18:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Dec 2012 06:18:48 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [66.111.4.28] (HELO out4-smtp.messagingengine.com) (66.111.4.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Dec 2012 06:18:41 +0000 Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1A67C20979 for ; Thu, 27 Dec 2012 01:18:21 -0500 (EST) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 27 Dec 2012 01:18:21 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=9VZpyiGguCdTkaAgGffYjuXzgDw=; b=gfJwirNIH6TF6FSxW+8nYI59NtFD UXIzWWHjUcNz2K/pQuQ9ScozX5QJzv4PySdWr/fxi0Tmq9qb/FDw3vYiMA5paR+T vkb8Lr2JuzkTfmPbDRjFApmPbkGBfnosLCjVMByMowrjVwt+oSVMO76/fHStm22y gjI4UW5FF5mYdqk= X-Sasl-enc: E4Fae2qTUrHtNB2LJEw5xJzYOr4hFzkpEQzIjHylah3P 1356589100 Received: from localhost (unknown [123.51.18.38]) by mail.messagingengine.com (Postfix) with ESMTPA id 2D54E8E06F8 for ; Thu, 27 Dec 2012 01:18:19 -0500 (EST) Date: Thu, 27 Dec 2012 17:18:17 +1100 From: David Crossley To: Gump code and data Subject: Re: help with "forrest-test" gump run Message-ID: <20121227061817.GB1303@igg.local> References: <20121221124559.GB39682@igg.local> <87txraobtl.fsf@v35516.1blu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87txraobtl.fsf@v35516.1blu.de> User-Agent: Mutt/1.4.2.3i X-Virus-Checked: Checked by ClamAV on apache.org Stefan Bodewig wrote: > David Crossley wrote: > > > > Help please with working out why the "forrest-test" run of Gump is broken. > > http://vmgump.apache.org/gump/public/forrest/forrest-test/ > > Sorry, have been (and likely will continue to be for the next few days) > mostly offline. Thanks, me too. > You have modified the build process enough that there > is no fetch-local-unversioned-plugin target to see in the log anymore. Yep, i am trying a completely different approach now. Deploying the plugins, then forcing the test to use them rather than forrest's fancy plugin finding mechanism. > Right now I see configure-plugin failing for PDF - is the where you'd > suppose the plugin to be downloaded? It is different now :-) This is fine, as i am gradually working to fix various things that Gump encounters. I reckon that it is on the home straight. > Looking through FOR-1235 and your XSL, you have > > > > which means the target would be skipped if the property plugin-found was > set for any reason. > > The Gump output you quote inside the JIRA ticket > really looks like the one you'd get if a target was skipped because of > an if/unless attribute. Drat, i should have updated the issue with a snippet from a more recent Gump run. I think that it got past that stage but completely missed the next "get-local". After this new approach is settled, i hope to make some time. Of course the challenge is to work out why the difference between a local build and the Gump one. > You certainly could be triggering a bug/feature in Ant or Ant-Contrib > present only in trunk but not the version you use locally, but neither > project has been really active lately so that's not too likely. > > Maybe you could build Ant from trunk and see whether your local build > still fails with that as well. Good idea. It has been a while since Forrest upgraded various dependencies, so a job that needs doing anyway. Thanks again for your efforts Stefan. -David --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org