| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Turelinckx <pgbf(at)twiska(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "ago" times on buildfarm status page |
| Date: | 2019-08-27 12:45:36 |
| Message-ID: | 4b4e1c05-e0a9-73d7-9589-c7d59777b5c9@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 repo as 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Asim R P | 2019-08-27 13:27:46 | Re: Fault injection framework |
| Previous Message | vignesh C | 2019-08-27 11:16:32 | Re: block-level incremental backup |