From: Janis Johnson <janis187@us.ibm.com>
To: Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org
Subject: Re: Meta-expectations when testing
Date: Wed, 26 Feb 2003 21:09:00 -0000 [thread overview]
Message-ID: <20030226124721.A2277@us.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.53.0302261807050.21556@neelix>; from hgs@dmu.ac.uk on Wed, Feb 26, 2003 at 06:41:48PM +0000
On Wed, Feb 26, 2003 at 06:41:48PM +0000, Hugh Sasse Staff Elec Eng wrote:
> On Wed, 26 Feb 2003, Janis Johnson wrote:
> > The first sentence in test.html (generated from gcc/doc/install.texi) is:
> >
> > Before you install GCC, we encourage you to run the testsuites and to
> > compare your results with results from a similar configuration that have
> > been submitted to the @uref{http://gcc.gnu.org/ml/gcc-testresults/,,
> > gcc-testresults mailing list}.
>
> Yes, but that is on the install page.
No, it's on the testing page, test.html, one of the 10 html files that
are generated from install.texi.
> > Would appending the following to that be sufficient?
> >
> > Some of these archived results are linked from the build status lists
> > at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
> > reports a successful build runs the testsuites and submits the results.
>
> Not on the install page, for the reasons above.
Yes, but would it help at the beginning of test.html?
> > (Also, the maintainer of the build status lists sometimes doesn't have
> > time to go through the gcc-testresults archives after a release to
> > include new reports in the build status list as she ought to, and
> > welcomes mail pointing out the URLs of such reports, or patches to the
> > status list.)
>
> There seems to be no address for a person on these pages, only for
> groups of people {gcc,gnu}@gnu.org, so I don't know who that is.
Sorry, that's me; I wouldn't imply that another volunteer is lazy.
Successful build reports to to gcc@gcc.gnu.org, as could informaiton
about the URLs for test results for a released compiler. A patch to add
test result URSs to a build status list could go to
gcc-patches@gcc.gnu.org.
Janis
next prev parent reply other threads:[~2003-02-26 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 21:04 Hugh Sasse Staff Elec Eng
2003-02-24 21:23 ` Janis Johnson
2003-02-25 11:08 ` Hugh Sasse Staff Elec Eng
2003-02-25 17:48 ` Janis Johnson
2003-02-26 10:18 ` Hugh Sasse Staff Elec Eng
2003-02-26 18:13 ` Janis Johnson
2003-02-26 20:17 ` Hugh Sasse Staff Elec Eng
2003-02-26 21:09 ` Janis Johnson [this message]
2003-02-27 13:59 ` Hugh Sasse Staff Elec Eng
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=20030226124721.A2277@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=hgs@dmu.ac.uk \
/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).