From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5857 invoked by alias); 2 Jul 2007 16:06:56 -0000 Received: (qmail 5828 invoked by uid 22791); 2 Jul 2007 16:06:56 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,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, 02 Jul 2007 16:06:54 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.43) id 1I5OSi-0004Sd-UH for frysk@sourceware.org; Mon, 02 Jul 2007 18:09:18 +0200 Subject: What does brokenIfUtraceXXX() test for? From: Mark Wielaard To: frysk@sourceware.org Content-Type: text/plain Date: Mon, 02 Jul 2007 16:06:00 -0000 Message-Id: <1183392408.3622.24.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) 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-q3/txt/msg00001.txt.bz2 Hi, I am seeing two failures on 2.6.21-1.3228.fc7 x86 SMP: testTerminateKillKILL(frysk.proc.TestTaskTerminateObserver)junit.framework.AssertionFailedError: terminating value expected:<-9> but was:<128> testTerminatingKillKILL(frysk.proc.TestTaskTerminateObserver)junit.framework.AssertionFailedError: terminating value expected:<-9> but was:<128> That are guarded by brokenIfUtraceXXX() which has as explanation: /** * A method that returns true, and prints broken, when the build * kernel includes UTRACE. */ So, tests guarded by that ever never expected to succeed with utrace enabled? Or is it more subtle than that? Both bugs referenced through these guards (#3525 and #3489) are closed already. Cheers, Mark