From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1368 invoked by alias); 29 May 2007 13:20:04 -0000 Received: (qmail 1354 invoked by uid 22791); 29 May 2007 13:20:03 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,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; Tue, 29 May 2007 13:19:58 +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 l4TDJdNC002010; Tue, 29 May 2007 09:19:39 -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 l4TDJd0S002375; Tue, 29 May 2007 09:19:39 -0400 Received: from [10.13.248.117] (vpn-248-117.boston.redhat.com [10.13.248.117]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4TDJbej007584; Tue, 29 May 2007 09:19:38 -0400 Subject: Re: Results of systemtap 20070526 snapshot on ppc64 From: Martin Hunt To: Srinivasa Ds Cc: systemtap@sources.redhat.com, Naren A Devaiah In-Reply-To: <465BB2C3.1010804@in.ibm.com> References: <465BB2C3.1010804@in.ibm.com> Content-Type: text/plain Organization: Red Hat Inc. Date: Tue, 29 May 2007 13:20:00 -0000 Message-Id: <1180444777.3894.1.camel@dragon> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00408.txt.bz2 On Tue, 2007-05-29 at 10:27 +0530, Srinivasa Ds wrote: > Results of this week systemtap-snapshot(20070526) on ppc64 looks like below. > FAIL: 64-bit mmap (PR 4472) > FAIL: 64-bit readwrite (PR 4472) > FAIL: 64-bit signal (PR 4472) > FAIL: 32-bit clock (PR 4472) > FAIL: 32-bit mmap (PR 4472) > FAIL: 32-bit readwrite (PR 4472) > FAIL: 32-bit signal (PR 4472) 4472 is waiting for feedback. Please read the comments there and post detailed failures in that PR so we can get these fixed. Martin