From: Audrius Meskauskas <audriusa@bluewin.ch>
To: Mauve discuss <mauve-discuss@sourceware.org>
Subject: Re: Mauve wishlist
Date: Fri, 17 Mar 2006 22:34:00 -0000 [thread overview]
Message-ID: <441B3990.6060306@bluewin.ch> (raw)
In-Reply-To: <1142613140.3805.20.camel@rh-ibm-t41>
1. My largest problem was hangings during the tests. When an error
report is just an error report, hanging blocks all testing process,
requiring to remove such test manually. The problem is difficult to
solve, but maybe the tests could run in the separate thread, and the
threads of the normally terminated tests could be reused. JUnit, by the
way, also has the same problem.
2. Probably the error reports could include the line, where the harness
check failed. The stack trace of the newly constructed exception could
be used to get the line information. The uncaught exception reports
could also provide more information, not just "uncaught exception", as
it is now.
Regards
Audrius Meskauskas.
next prev parent reply other threads:[~2006-03-17 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 16:27 Thomas Fitzsimmons
2006-03-17 21:06 ` David Daney
2006-03-18 8:15 ` Michael Koch
2006-03-17 22:34 ` Audrius Meskauskas [this message]
2006-03-20 10:53 ` Arnaud Vandyck
2006-03-20 16:51 ` Anthony Balkissoon
2006-03-21 16:58 ` David Gilbert
2006-03-21 22:24 ` Tom Tromey
2006-03-21 23:08 ` Bryce McKinlay
2006-03-22 11:12 ` David Gilbert
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=441B3990.6060306@bluewin.ch \
--to=audriusa@bluewin.ch \
--cc=mauve-discuss@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: link
Be 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).