From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31168 invoked by alias); 10 Feb 2007 00:31:34 -0000 Received: (qmail 31148 invoked by uid 22791); 10 Feb 2007 00:31:32 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 10 Feb 2007 00:31:27 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1A0VPbr008212 for ; Fri, 9 Feb 2007 19:31:25 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1A0VOVF020018 for ; Fri, 9 Feb 2007 19:31:24 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1A0VOQP013150 for ; Fri, 9 Feb 2007 19:31:24 -0500 Message-ID: <45CD125C.7060803@redhat.com> Date: Sat, 10 Feb 2007 00:31:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: frysk@sourceware.org Subject: Added frysk.junit.TestCase.brokenIfKernel(int bug, String[] kernels) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00103.txt.bz2 FYI, I've added the generic method: frysk.junit.TestCase.brokenIfKernel(int bug, String[] kernels) to make it easier to mark up a specific combination of bug and kernel. I've used that to disable some of the TestBreakpoint tests on fc5.18 systems and get frysk-core on that system passing again. Its always important to ensure that the JUnit tests, on all systems, get no failures. 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. Andrew