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 4b4e1c05-e0a9-73d7-9589-c7d59777b5c9@2ndQuadrant.com
Whole thread Raw
In response to Re: "ago" times on buildfarm status page  ("Tom Turelinckx" <pgbf@twiska.com>)
Responses Re: "ago" times on buildfarm status page  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
On 8/27/19 4:33 AM, Tom Turelinckx wrote:
> 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.
>>
>> This is the kind of old-fashioned way of doing things. These days "git_keep_mirror => 1" along with the community
repoas the base would avoid these problems.
 
> We've discussed this before (see below).
>
>
>  Hm. So the issue really is that the build timestamp that the buildfarm
>  client is reporting tells when it pulled from the local repo, not when
>  that repo was last updated from the community server. Not sure if there's
>  any simple way to improve that ... Andrew, any thoughts?



Maybe we need an option to use the git commit time. instead of the
snapshot time.


cheers


andrew


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




pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: block-level incremental backup
Next
From: Asim R P
Date:
Subject: Re: Fault injection framework