From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29350 invoked by alias); 10 Mar 2008 10:55:24 -0000 Received: (qmail 29342 invoked by uid 22791); 10 Mar 2008 10:55:24 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 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, 10 Mar 2008 10:55:07 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1JYfep-0005et-P0 for frysk@sourceware.org; Mon, 10 Mar 2008 11:55:04 +0100 Subject: 2.6.24.3-12.fc8 kernel on x86 breaks frysk test suite From: Mark Wielaard To: frysk Content-Type: text/plain Date: Mon, 10 Mar 2008 10:55:00 -0000 Message-Id: <1205146503.3356.16.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8) 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: 2008-q1/txt/msg00140.txt.bz2 Hi, Be careful upgrading your fedora kernel, at least on x86. The way the frysk test suite does a teardown seems to play havoc with the new kernel leading to strange kill messages and TestRunner just completely stopping. With 2.6.24.3-12.fc8 on x86 a make check almost always fails (x86_64 seems fine though). Downgrading to 2.6.23.15-137.fc8 makes make check (at least in frysk-core) completely clean again. With the newer kernel tests fail (and the TestRunner gets killed!) somewhat randomly. It is easily reproducible through something like: ./TestRunner -r 100 frysk.proc.TestTaskTerminateObserver Which makes things a little worse by throwing in some kills of its own. And it always fails within a couple of rounds with as output: frysk.sys.Errno$Einval: tkill: Invalid argument (task 0) I filed it as bug #5902. It is somewhat nasty in that it isn't very predictable where/when it breaks things. And I spend some time trying to bisect patches till it occurred to me that it might have been the kernel upgrade. Cheers, Mark