From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22904 invoked by alias); 27 Jun 2006 16:38:35 -0000 Received: (qmail 22784 invoked by uid 22791); 27 Jun 2006 16:38:33 -0000 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; Tue, 27 Jun 2006 16:38:32 +0000 Received: from elsschot.wildebeest.org ([192.168.1.26]) by gnu.wildebeest.org with esmtp (Exim 3.36 #1 (Debian)) id 1FvGb3-0004NV-00; Tue, 27 Jun 2006 18:39:29 +0200 Subject: Re: RFC: add "not-a-test" tag to several tests From: Mark Wielaard To: Thomas Fitzsimmons Cc: Anthony Balkissoon , mauve-patches@sources.redhat.com In-Reply-To: <44A15734.8030708@redhat.com> References: <1151080291.25174.104.camel@tony.toronto.redhat.com> <1151331641.3361.8.camel@localhost.localdomain> <1151332775.2701.16.camel@elsschot.wildebeest.org> <44A00DF9.9040306@redhat.com> <1151340576.2557.3.camel@elsschot.wildebeest.org> <44A15734.8030708@redhat.com> Content-Type: text/plain Date: Tue, 27 Jun 2006 16:38:00 -0000 Message-Id: <1151426293.2555.79.camel@elsschot.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact mauve-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-patches-owner@sourceware.org X-SW-Source: 2006/txt/msg00487.txt.bz2 Hi, On Tue, 2006-06-27 at 12:05 -0400, Thomas Fitzsimmons wrote: > > I know, but that is a terrible way for debugging. Hunting down a crasher > > bug for example is really, really awkward using the Harness since it > > does way too many things. When examining tests (especially under gdb) > > for debugging you need to be able to run them just through the > > RunnerProcess to make sure you are looking at just the thing that fails. > > It works nicely with that one-liner patch though, so it isn't really > > another way to run tests, it is just to make sure you can run the tests > > by hand as if the Harness would run them. > > Why don't we just print the VM command-line invocation as part of Harness's > output? Then you could simply copy-n-paste that to gdb --args. Sure as long as what gets invoked is really just the testcase and nothing else. We use Mauve for low level tests of both the core library and the runtimes so we really don't want too much things like Sockets or fancy reflection constructs in the TestRunner itself. Cheers, Mark