From: Daniel Berlin <dberlin@dberlin.org>
To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
Cc: Volker Reichelt <reichelt@igpm.rwth-aachen.de>, gcc@gcc.gnu.org
Subject: Re: Testcases in Bugzilla
Date: Tue, 13 May 2003 21:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305131723380.13797@dberlin.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0305131545510.23882-100000@gandalf.ices.utexas.edu>
On Tue, 13 May 2003, Wolfgang Bangerth wrote:
>
> > we still haven't reached a conclusion about the testcases in Bugzilla.
>
> To be quite honest, I think what you suggest won't work. What we put into
> the bug database is just too diverse:
> - we have bug reports where just the text of an error message became
> worse than before
> - we have bug reports where we get the compiler into an endless loop
> - we have reports where compilation takes quadratic instead of linear
> time in the input
> - reports with two or more testcases that should do the same but don't
> - some other really weird stuff happening.
>
> I can't imagine a method to _automatically_ extract these testcases and do
> something reasonable. If there is one, it would increase the entry level
> for people working in GNATS.
Err, we can easily extract attachments marked "testcase" from bugzilla in
about 9 lines of perl.
The rest is up to other scripts and whatnot.
>
>
>
next prev parent reply other threads:[~2003-05-13 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:56 Wolfgang Bangerth
2003-05-13 21:25 ` Daniel Berlin [this message]
2003-05-13 21:26 ` Wolfgang Bangerth
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 11:50 Volker Reichelt
2003-05-13 18:33 ` Janis Johnson
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=Pine.LNX.4.53.0305131723380.13797@dberlin.org \
--to=dberlin@dberlin.org \
--cc=bangerth@ices.utexas.edu \
--cc=gcc@gcc.gnu.org \
--cc=reichelt@igpm.rwth-aachen.de \
/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).