From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Darcy Buskermolen <darcy(at)wavefire(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: OK, ready for RC1 or Beta6 |
Date: | 2004-12-03 22:41:28 |
Message-ID: | 41B0EB98.7010909@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>
>>Tom Lane wrote:
>>
>>
>>>It's too bad the buildfarm reports don't show more details about what
>>>CVS pull they're using exactly.
>>>
>>>
>
>
>
>>Snapshot is the UTC time at which the cvs pull was done.
>>
>>
>
>That's good but it's of limited use to me, since the snaps are (I
>presume) against the anonymous-CVS server which lags commits on the
>master by I'm-not-sure-how-much.
>
>
In my case it's against my local CVSup mirror, which is updated every 15
minutes. The buildfarm config lets you choose what repo to use.
Nevertheless I take your point.
>
>
>>Clients report
>>what files have changed since the last run, and also, in the case of a
>>failure, what files have changed since the last successful run.
>>
>>
>
>Cool, I had not seen it do that before. If we could get the CVS version
>number of each mentioned file into that, it would go a long way towards
>helping identify exactly what's being tested.
>
>
Feature request filed on pgfoundry - not sure when I'll get to it.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-12-03 22:58:55 | Re: somebody working on: Prevent default re-use of sysids for dropped users and groups? |
Previous Message | Tom Lane | 2004-12-03 22:29:38 | Re: Buildfarm coverage (was Re: OK, ready for RC1 or Beta6) |