X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 10E9CD1B538 for ; Tue, 18 Nov 2003 19:36:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 95865-08 for ; Tue, 18 Nov 2003 15:36:23 -0400 (AST) Received: from trolak.mydnsbox2.com (ns1.mydnsbox2.com [207.44.142.118]) by svr1.postgresql.org (Postfix) with ESMTP id 6C622D1C954 for ; Tue, 18 Nov 2003 15:36:21 -0400 (AST) Received: from dunslane.net (x.ncshp.org [199.90.235.43]) (authenticated (0 bits)) by trolak.mydnsbox2.com (8.11.6/8.11.6) with ESMTP id hAIKXLQ29590 for ; Tue, 18 Nov 2003 14:33:21 -0600 Message-ID: <3FBA74B7.2090106@dunslane.net> Date: Tue, 18 Nov 2003 14:36:23 -0500 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Postgresql Hackers Subject: Build farm References: <87smkmgyn7.fsf@mailbox.samurai.com> <20031117233828.Y731@ganymede.hub.org> <200311180942.31093.josh@agliodbs.com> <3FBA6999.9030906@dunslane.net> <20031118151211.U731@ganymede.hub.org> In-Reply-To: <20031118151211.U731@ganymede.hub.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/1003 X-Sequence-Number: 47291 Marc G. Fournier wrote: >On Tue, 18 Nov 2003, Andrew Dunstan wrote: > > > >>Maybe some sort of automated distributed build farm would be a good >>idea. Check out http://build.samba.org/about.html to see how samba does >>it (much lighter than the Mozilla tinderbox approach). >> >>We wouldn't need to be as intensive as they appear to be - maybe a once >>or twice a day download and test run would do the trick, but it could >>pick up lots of breakage fairly quickly. >> >>That is not to say that more intensive testing isn't also needed on >>occasion. >> >> > >Check the archives on this, as its been hashed out already once at least >... I think the big issue/problem is that nobody seems able (or wants) to >come up with a script that could be setup in cron on machines to do this >... something simple that would dump the output to a log file and, if >regression tests failed, email'd the machine owner that it needs to be >checked would do, I would think ... > If there's general interest I'll try to cook something up. (This kind of stuff is right up my alley). I'd prefer some automated display of results, though. A simple CGI script should be all that's required for that. cheers andrew