From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12276 invoked by alias); 21 Jun 2008 14:18:18 -0000 Received: (qmail 12269 invoked by uid 22791); 21 Jun 2008 14:18:18 -0000 X-Spam-Status: No, hits=-2.5 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, 21 Jun 2008 14:18:01 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m5LEHwJw003446 for ; Sat, 21 Jun 2008 10:17:59 -0400 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 m5LEHw09007249 for ; Sat, 21 Jun 2008 10:17:58 -0400 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 m5LEHqPv025740 for ; Sat, 21 Jun 2008 10:17:53 -0400 Message-ID: <485D0D9F.2050209@redhat.com> Date: Sat, 21 Jun 2008 15:02:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: frysk Subject: Re: running tests under jni References: <485BB46A.50303@redhat.com> In-Reply-To: <485BB46A.50303@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 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: 2008-q2/txt/msg00114.txt.bz2 PS: I fixed two problems, on a dual-core AMD64 running F-8: under JNI there are ~9 failures, while under CNI ~8 -> i.e. "bug compatible". really cu in a week :-) Andrew Cagney wrote: > FYI, > > I've just completed my first full run of frysk-core's test-suite under > JNI; and have gone through and filed bugs for each class of failure. > Including the failures I also see under CNI (~6), I came up with 14 > unique cases (while there's a small number of problems they are > affecting ~60 of the tests). > > More useful, I think, is this: > > $ make jni > $ ./JniRunner > > as away to quickly turn around your work-in-progress code. Of course, > a full TestRunner run is still expected. > > cu all a bit over a week (perhaps I'll come back to find some of the > bugs fixed :-) > > Andrew >