Re: "ago" times on buildfarm status page - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: "ago" times on buildfarm status page
Date
Msg-id 342862a8-7780-521e-d52c-146bcba0519b@2ndQuadrant.com
Whole thread Raw
In response to Re: "ago" times on buildfarm status page  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 8/27/19 10:15 AM, Tom Lane wrote:
> "Tom Turelinckx" <pgbf@twiska.com> writes:
>> On Mon, Aug 26, 2019, at 9:08 PM, Andrew Dunstan wrote:
>>> I think this is the problem:
>>> 'scmrepo' => '/home/pgbf/pgmirror.git',
>>> Probably this isn't updated often enough. It probably has little to do with the clock settings.
>> The configuration is intentionally like that. I specifically configured skate and snapper to build the exact same
source,where skate builds with default buildfarm settings, while snapper builds with the settings actually used by
Debiansource packages.
 
> TBH, I don't find that particularly important ... especially not for HEAD
> builds, where building a many-hours-old snapshot is pretty much in the
> category of "why bother?".  On the whole, I think building from the latest
> available source is the most useful policy.  If there's some platform-
> or configuration-specific issue, it usually takes more than one build
> cycle for us to notice it anyway, so that ensuring two animals have exactly
> comparable builds at any given instant isn't very helpful.
>
>             



Yeah, point. snapper seems the more important box here.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: range bug in resolve_generic_type?
Next
From: Tom Lane
Date:
Subject: Re: old_snapshot_threshold vs indexes