From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Buildfarm feature request: some way to track/classify failures |
Date: | 2007-03-20 19:00:15 |
Message-ID: | 46002F3F.3030501@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Tom Lane wrote:
>> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>>
>>> But I'm just sprouting ideas here, the proof is in the pudding. If the
>>> logs are easily available (or a subset of, say the last month) then
>>> people could play with that and see what happens...
>>>
>>
>> Anyone who wants to play around can replicate what I did, which was to
>> download the table that Andrew made available upthread, and then pull
>> the log files matching interesting rows.
> [snip]
>
>
> To save people this trouble, I have made an extract for the last 3
> months, augmented by log field, which is pretty much the last stage log.
> The dump is 27Mb and can be got at
>
> http://www.pgbuildfarm.org/tfailures.dmp
Should we just automate this and make it a weekly?
>
> cheers
>
> andrew
>
>
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-03-20 19:05:50 | Re: Stats for multi-column indexes |
Previous Message | Andrew Dunstan | 2007-03-20 18:46:01 | Re: Buildfarm feature request: some way to track/classify failures |