From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | buildfarm happenings |
Date: | 2005-08-04 16:09:33 |
Message-ID: | 42F23DBD.1040103@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
If you haven't visited the buildfarm recently you might have missed a
few developments:
. we are now reporting flags used on builds on the main dashboard page -
I am working on making that look nicer by using icons - see
http://www.pgbuildfarm.org/cgi-bin/show_status4.pl for prgress.
. the latest release provides for uploading all the log files, not just
the log from the error stage. The details page for each build provides a
link to each log file if they are present. Many buildfarm members are
already running prerelease version of this facility.
. Eric Astor at EnterpriseDB is using a modified client on his member
"finch" to run the Coverity static source code analysis tool, and the
results are uploaded along with the rest of the log files - see for
example
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=finch&dt=2005-08-03%2020:12:42
All this and more is supported by the latest release, fresh today, of
the client code, available on pgfoundry, the notes for which state:
Feature: upload a zipped tar of all the logs, regardless of success status
Feature: --from-source option lets you test changes in a locally
modified repo copy
Feature: Cygwin cygrunserv sanity check
Feature: Add integrity checking for CVS conflicts and locally modified
files.
Fixes: multiroot and keeperror modes fixed.
--from-source is not yet documented, but enables you to use the
buildfarm client as a testing tool for changes made in a repo copy.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-04 16:20:24 | Re: Solving the OID-collision problem |
Previous Message | Tino Wildenhain | 2005-08-04 15:59:41 | Re: pg_dump -- data and schema only? |