From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13617 invoked by alias); 12 Feb 2007 12:09:30 -0000 Received: (qmail 13607 invoked by uid 22791); 12 Feb 2007 12:09:29 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_05,FORGED_RCVD_HELO X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 12 Feb 2007 12:09:25 +0000 Received: from hermans.wildebeest.org ([192.168.1.28]) by gnu.wildebeest.org with esmtp (Exim 4.43) id 1HGa0T-0003xj-T3; Mon, 12 Feb 2007 13:10:06 +0100 Subject: Re: Added frysk.junit.TestCase.brokenIfKernel(int bug, String[] kernels) From: Mark Wielaard To: Andrew Cagney Cc: frysk@sourceware.org In-Reply-To: <45CD125C.7060803@redhat.com> References: <45CD125C.7060803@redhat.com> Content-Type: text/plain Date: Mon, 12 Feb 2007 12:09:00 -0000 Message-Id: <1171282158.3010.5.camel@hermans.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 (2.8.2.1-3.fc6) Content-Transfer-Encoding: 7bit X-Spam-Score: -2.8 (--) X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00104.txt.bz2 Hi Andrew, On Fri, 2007-02-09 at 19:31 -0500, Andrew Cagney wrote: > Where a failure is occurring on a specific kernel, try to > fix it, or at least mark it up as a known breakage. By doing this, > people always have access to a failure free starting point, and with out > it, no one is ever sure if their change or existing breakage is causing > a failure. Although I don't mind people blacklisting some tests on their systems because of buggy kernel, compiler, libaudit, etc. to make some things more convenient for them. I am not sure how maintainable that is. We do have explicit tests for broken systems in frysk-import/tests. If a developer is working on a system that is know to be broken and buggy (because they have frysk-import/tests fail one or more checks) it seems that they better make sure to fix the bug in the dependencies and/or migrate to a non-broken system. Otherwise they will be running into trouble sooner or later anyway. And the skipped tests only paper over the problem that will come back and bite them later on during development. Cheers, Mark