Return-Path: X-Original-To: pgbuildfarm-members@lists.pgfoundry.org Delivered-To: pgbuildfarm-members@lists.pgfoundry.org Received: from localhost (unknown [188.227.186.44]) by pgfoundry.org (Postfix) with ESMTP id 014EB13C195A for ; Mon, 12 Sep 2016 01:08:38 +0000 (UTC) Received: from pgfoundry.org ([188.227.186.71]) by localhost (maia-lon.uk.hub.org [188.227.186.44]) (maiad, port 10024) with ESMTP id 42829-05 for ; Mon, 12 Sep 2016 01:08:37 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pgfoundry.org (Postfix) with ESMTPS id B431313C1953 for ; Mon, 12 Sep 2016 01:08:37 +0000 (UTC) Received: from mfilter35-d.gandi.net (mfilter35-d.gandi.net [217.70.178.166]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 4A1DBA80C6; Mon, 12 Sep 2016 03:08:37 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter35-d.gandi.net Received: from relay3-d.mail.gandi.net ([IPv6:::ffff:217.70.183.195]) by mfilter35-d.gandi.net (mfilter35-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id zpnjb_uPt1R5; Mon, 12 Sep 2016 03:08:35 +0200 (CEST) X-Originating-IP: 98.122.164.227 Received: from [192.168.10.146] (unknown [98.122.164.227]) (Authenticated sender: adsend@dunslane.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id D5EF7A80C2; Mon, 12 Sep 2016 03:08:34 +0200 (CEST) To: Tom Lane , Daniel Black References: <411d52c0-247a-21ea-d1e5-1711c08c8616@au.ibm.com> <7deab5c6-ee6b-256b-ac1a-92c8b4bf3233@dunslane.net> <7190.1473641374@sss.pgh.pa.us> From: Andrew Dunstan Message-ID: Date: Sun, 11 Sep 2016 21:08:33 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <7190.1473641374@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: pgbuildfarm-members@lists.pgfoundry.org Subject: Re: [Pgbuildfarm-members] docker instances of pgbuildfarm X-BeenThere: pgbuildfarm-members@lists.pgfoundry.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2016 01:08:38 -0000 Status: RO Content-Length: 1121 Lines: 34 On 09/11/2016 08:49 PM, Tom Lane wrote: > Daniel Black writes: >> Relax, the git updates are done outside of the pgbuildfarm scripts. >> Below is the start of the log that triggered the build this morning. > The problem with inventing your own approach here is that your buildfarm > members' reports do not provide any evidence of what they are building > against. Please examine > > http://buildfarm.postgresql.org/cgi-bin/show_status.pl > > and note that your animals are not showing last-commit-id in their lines > on the summary page, and if you drill down to their build reports, those > don't show anything about "changes since last run" either, eg compare > > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=demoiselle&dt=2016-09-12%2000%3A36%3A03 > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=guaibasaurus&dt=2016-09-12%2000%3A17%3A01 > > That greatly reduces the usefulness of the reports. > > I also don't see any point in doing this. Please run this software as intended. (BTW, telling someone to relax is quite offensively patronizing.) cheers andre