From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21779 invoked by alias); 13 Jan 2010 20:58:19 -0000 Received: (qmail 21683 invoked by uid 48); 13 Jan 2010 20:58:06 -0000 Date: Wed, 13 Jan 2010 20:58:00 -0000 Message-ID: <20100113205806.21682.qmail@sourceware.org> From: "dsmith at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070508113924.4472.srinivasa@in.ibm.com> References: <20070508113924.4472.srinivasa@in.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug testsuite/4472] sytemtap.syscall failures on ppc64. X-Bugzilla-Reason: AssignedTo 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: 2010-q1/txt/msg00114.txt.bz2 ------- Additional Comments From dsmith at redhat dot com 2010-01-13 20:58 ------- On ppc64 (kernel 2.6.18-164.el5), with current systemtap (after the bug #11167 fix), I'm only seeing 1 syscall testsuite failure on ppc64. ==== Running /root/src/testsuite/systemtap.syscall/syscall.exp ... FAIL: 64-bit signal === systemtap Summary === # of expected passes 57 # of unexpected failures 1 # of unsupported tests 2 ==== As mentioned in bug #4425, the lone failure in the 64-bit signal test is due to the kernel not implementing the sigaction and sigprocmask calls for 64-bit executables. -- What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED http://sourceware.org/bugzilla/show_bug.cgi?id=4472 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.