From: Richard Earnshaw <rearnsha@arm.com>
To: Carlo Wood <carlo@runaway.xs4all.nl>
Cc: rearnsha@sun52.arm.com
Subject: Re: Will the consistent failures in EGCS be fixed soon?
Date: Fri, 26 Jun 1998 13:03:00 -0000 [thread overview]
Message-ID: <199806261515.QAA00384@sun52.NIS.cambridge> (raw)
In-Reply-To: <199806261204.OAA25577@jolan.ppro>
> | Ok, I'll buy that; so how about another document describing known
> | failures, and the part of the compiler responsible -- this might help to
> | save hours of wasted work trying to track down the cause of problems that
> | have already been investigated but not yet fixed.
> |
> | Richard
>
> This `database' could grow pretty large.
> I imagine that a sort of E-mail thread on each test case, kept
> on the website would be favourable above including it in the
> tar.gz.
>
Not necessarily. Broken tests get fixed, in which case the need to
document the cause of the ex-failure goes away. Working tests don't need
any documentation. Of course, the test may fail again at some later date,
but that will need investigation in its own right; I'd guess the chance
that the same reason would be the cause of a future failure (assuming the
problem was fixed properly in the first place) would be no more than 50/50.
Richard.
next prev parent reply other threads:[~1998-06-26 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-23 21:11 Benjamin Redelings I
1998-06-24 10:08 ` Horst von Brand
1998-06-24 15:17 ` Martin von Loewis
1998-06-25 0:25 ` Jeffrey A Law
1998-06-24 17:12 ` Benjamin Redelings I
1998-06-25 6:50 ` Richard Earnshaw
1998-06-25 9:25 ` Jeffrey A Law
1998-06-25 12:33 ` Richard Earnshaw
1998-06-25 15:59 ` Jeffrey A Law
1998-06-26 13:03 ` Carlo Wood
1998-06-26 13:03 ` Richard Earnshaw [this message]
1998-06-29 19:00 Mike Stump
1998-06-29 19:43 Mike Stump
1998-06-29 20:41 ` Jeffrey A Law
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=199806261515.QAA00384@sun52.NIS.cambridge \
--to=rearnsha@arm.com \
--cc=carlo@runaway.xs4all.nl \
--cc=rearnsha@sun52.arm.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).