public inbox for [email protected]  

help / color / mirror / Atom feed

From: Daniel Black <[email protected]>
To: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: [Pgbuildfarm-members] docker instances of pgbuildfarm
Date: Mon, 12 Sep 2016 11:25:21 +1000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
List-Unsubscribe:  <http://lists.pgfoundry.org/mailman/options/pgbuildfarm-members>, <mailto:[email protected]?subject=unsubscribe>



On 12/09/16 11:08, Andrew Dunstan wrote:
> 
> 
> On 09/11/2016 08:49 PM, Tom Lane wrote:
>> Daniel Black <[email protected]> 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.

so I see.

> I also don't see any point in doing this.

Mainly fitting in with current infrastructure.

> Please run this software as intended.

Will look into it.

> (BTW, telling someone to relax is quite offensively patronizing.)

Wasn't intended. Sorry.

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [Pgbuildfarm-members] docker instances of pgbuildfarm
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox