Re: Geometry regression test failure, CVS HEAD, Mac OS/X

From: Gaetano Mendola <mendola(at)bigfoot(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Geometry regression test failure, CVS HEAD, Mac OS/X
Date: 2004-09-08 23:12:37
Message-ID: 413F91E5.8050401@bigfoot.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:

>
>
> David Fetter wrote:
>
>> Kind people,
>>
>> Lately (past 3 days or so, but I don't know exactly how far back this
>> goes), I've been getting some regression test failures for geometry
>> with CVS HEAD on OS/X.
>>
>>
>
> We have seen a number of reports recently of things broken some time in
> the past. As I am currently thinking about what I want to do in the next
> dev cycle, this might be an opportune time for me to raise again my
> previous suggestion of a distributed build farm, so we get timely and
> automated warnings of breakage. I started creating a script to do this,
> but got sidetracked onto more important things (like Windows stuff, CSV,
> dollar quoting), but I am prepared to restart the effort if enough
> people are interested. Essentially, this would involve installation of a
> perl script to be run from cron (or Windows equivalent - automating the
> build for Windows might be challenging ...), which would check out code
> from CVS, run "configure; make check" and then send the results to a
> central URL. Centrally, we would store the results and have a summary
> page, with access to full logs if necessary in case of errors.
>
> How we classify the results is also an open question. So far my thoughts
> are to classify by <Architecture,OS+Version,Compiler+Version>.
>
> Thoughts?

This can be a good model to follow:

http://boost.sourceforge.net/regression-logs/

Regards
Gaetano Mendola

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-09-08 23:17:04 Re: Making AFTER triggers act properly in PL functions
Previous Message Stephan Szabo 2004-09-08 23:10:33 Re: Making AFTER triggers act properly in PL functions