public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3839] New: funit print meaningfull error messages, not stack backtraces Date: Sat, 06 Jan 2007 10:56:00 -0000 [thread overview] Message-ID: <20070106105619.3839.cagney@redhat.com> (raw) 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.
next reply other threads:[~2007-01-06 10:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-06 10:56 cagney at redhat dot com [this message] 2007-01-08 18:41 ` [Bug general/3839] " npremji at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070106105619.3839.cagney@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).