From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13632 invoked by alias); 6 Jan 2007 10:56:33 -0000 Received: (qmail 13520 invoked by uid 48); 6 Jan 2007 10:56:20 -0000 Date: Sat, 06 Jan 2007 10:56:00 -0000 From: "cagney at redhat dot com" To: frysk-bugzilla@sourceware.org Message-ID: <20070106105619.3839.cagney@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/3839] New: funit print meaningfull error messages, not stack backtraces X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00041.txt.bz2 List-Id: vis: ./TestRunner frysk.proc.TestAbandon.testAbandonAndAbandonX Running testAbandonAndAbandonX(frysk.proc.TestAbandon) ...FAIL junit.framework.AssertionFailedError: Method "testAbandonAndAbandonX" not found Time: 0.006 There was 1 failure: 1) testAbandonAndAbandonX(frysk.proc.TestAbandon)junit.framework.AssertionFailedError: Method "testAbandonAndAbandonX" not found at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner) it should print an error message and fail before running any tests. When it comes to command line programs, error messages at the start, are better than stack backtraces. -- Summary: funit print meaningfull error messages, not stack backtraces Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: cagney at redhat dot com OtherBugsDependingO 2242 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=3839 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.