This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Meta-expectations when testing
On Wed, 26 Feb 2003, Janis Johnson wrote:
> 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.
*Sorry*, I misread that -- trying to read it too quickly!
>
> > > 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?
Yes, it would. Further apologies for my braindead response. Thank
you for your patience.
>
> > > (Also, the maintainer of the build status lists sometimes doesn't have
> > > time to go through the gcc-testresults archives after a release to
[...]
> > There seems to be no address for a person on these pages, only for
> > groups of people {gcc,gnu} at gnu dot org, so I don't know who that is.
>
> Sorry, that's me; I wouldn't imply that another volunteer is lazy.
Absolutely not: I read that as being *busy*. Thank you.
>
> Successful build reports to to gcc at gcc dot gnu dot 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 at gcc dot gnu dot org dot
OK.
>
> Janis
>
Thank you again,
Hugh