| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Buildfarm feature request: some way to track/classify failures |
| Date: | 2007-03-19 21:27:47 |
| Message-ID: | 45FF0053.2050705@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
>> 2. I was annoyed repeatedly that some buildfarm members weren't
>> reporting log_archive_filenames entries, which forced going the long
>> way round in the process I was using. Seems like we need some more
>> proactive means for getting buildfarm owners to keep their script
>> versions up-to-date. Not sure what that should look like exactly,
>> as long as it's not "you can run an ancient version as long as you
>> please".
>>
>>
>>
>
> Modern clients report the versions of the two scripts involved (see
> script_version and web_script_version in reported config) so we could
> easily enforce a minimum version on these.
>
Meanwhile, the owner of the main 2 offending machines has said he will
upgrade them.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luis D. García | 2007-03-19 22:16:57 | Make TIMESTAMP + TIME in the source code |
| Previous Message | Andrew Dunstan | 2007-03-19 21:25:13 | Re: Buildfarm feature request: some way to track/classify failures |