From owner-freebsd-stable Mon Oct 21 2:27:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C986C37B401 for ; Mon, 21 Oct 2002 02:27:53 -0700 (PDT) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE33A43E65 for ; Mon, 21 Oct 2002 02:27:52 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from cerberus.publity.de ([213.61.128.135] helo=snafu.de) by clever.eusc.inter.net with asmtp (Exim 3.36 #4) id 183Yqk-0005Oc-00; Mon, 21 Oct 2002 11:27:50 +0200 Message-ID: <3DB3C877.7080904@snafu.de> Date: Mon, 21 Oct 2002 11:27:19 +0200 From: "Fischer, Oliver" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021015 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Mike Hoskins Cc: Chris BeHanna , FreeBSD-Stable Subject: Re: freebsd test matrix References: <20021018134020.D8827-100000@fubar.adept.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry for my very late answer, I had to do some assigments for my university. Mike Hoskins wrote: > Clearly, this process indicates developers should write test cases for > their code... Unfortuneately, the last thing an opensource project needs > is more work for the developers. :) Yes, I know this argument but I think it isn't true. Only the start is hard but if you have a working test system you are much more flexible because you are not afraid that changes can break the system and you don't realize it. I know this from my own projects. Often little changes here broke code there. :-( > Of course it would be nice to someday have a fully automated, robust > test/stress setup for builds... That will involve a lot of work from > build/QA people and developers. So, in the meantime, what can we do to > provide a resource that is immediately available, and serves to gather > initiative for future projects? It needs even a lot of time to develop such a testsystem. It must be flexible, extensible, modular AND fast. I guess I needs some months to reach a state, that other people could integrate their stuff. > provide a resource that is immediately available, and serves to gather > initiative for future projects? > Would a site that simply let people post hardware specs, kernel configs, > dmesg output, debugging info, etc. be useful? I think maintaining a > searchable, user-supported database of build results would be a useful > first step toward something much larger. Ja, that is a good idea. Any concreate ideas how to do it? I would take part in it. BYe Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message