public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: Mike Simons <msimons@saic1.com>
Cc: egcs@cygnus.com
Subject: moving testcase submissions to testsuite
Date: Mon, 23 Feb 1998 13:07:00 -0000	[thread overview]
Message-ID: <19980223102932.34051@dgii.com> (raw)

Mike Simons wrote:

>   Speaking of testcases... do all of the short code bug examples reports 
> posted to this list turn themselves into additional testsuite cases?

Unfortunately, bits in the $MAIL stream don't magically mutate into
source code bits in gcc/testsuite/*.  A human has to do it.  Sometimes
a human will do it - I've noticed that Mark Mitchell in partcular is
really good about "here's a test case that fails, here's a patch to fix
it, and here's a testsuite entry to ensure that this never fails again".

It doesn't look like anyone has been scanning the lists and jamming them
into testcases.  This would be a lovely task for someone with a few
hours on their hands to help improve the quality of the compiler even if
you're not an industrial grade RTL wizard.

I've just picked through the EGCS-BUGS archives and pulled out all the
messages that look like they contain something that might be useful
to stick into testsuite cases.  (These are the ones that weren't
installation or bootstrap problem or followed up by "your code is
broken", etc.) There are still something like 800 of them.  After I get
them whittled down a little more I will try to work out a strategy for
reducing the working set down to a more manageable number.  I would
welcome some help in the process. 

A depressing percentage of the cases seemed to be g++ aborting when
faced with some of those newfangled language features.   That's just
an impression.

>   If not, how should they be packaged so they *are* added to the 
> regression suite?  (I don't know how dejagnu works)

Look in gcc/testsuite/*/* for examples.  "When in dejagnu, acts as the 
dejagnudists do."

>   Is posting information about failed tests useful?  (test name, it's 
> exit code... maybe a backtrace)

If you have a target that isn't well covered by the regular testers,
there's probably some value in it.  There are a couple folks that have
automated the build/test process routinely post the results.


RJL

                 reply	other threads:[~1998-02-23 13:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19980223102932.34051@dgii.com \
    --to=robertl@dgii.com \
    --cc=egcs@cygnus.com \
    --cc=msimons@saic1.com \
    /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).