From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: RFC: libc-testresults mailing list
Date: Wed, 02 Nov 2016 13:06:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611021254190.29297@digraph.polyomino.org.uk> (raw)
Andrew Pinski asked in
<https://sourceware.org/ml/libc-alpha/2016-07/msg00460.html> about a
mailing list for sending test results to.
I propose that we create a libc-testresults mailing list for test results
to be sent to by any kind of automation (not for discussions, if people
wish to discuss things about the results they should take replies to
libc-alpha with a meaningful Subject line rather than the subject line of
the results posting).
This would explicitly include results reporting on e.g. whether glibc
builds in various configurations, not just results of the glibc testsuite
itself. It would also include any systems automatically detecting
regressions and reporting on those regressions. It might be useful to
have something like GCC's contrib/test_summary to collect results and
information about the configuration and versions of various components
(and indeed for test runs to automatically record some information such as
the kernel version on the system, possibly remote, that test programs are
run on), but this is not required for such a list to be useful.
Comments?
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2016-11-02 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 13:06 Joseph Myers [this message]
2016-11-02 14:30 ` Carlos O'Donell
2016-11-02 16:48 ` Joseph Myers
2016-11-03 6:00 ` Andrew Pinski
2016-11-03 13:21 ` Joseph Myers
2016-11-21 19:08 ` Joseph Myers
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=alpine.DEB.2.20.1611021254190.29297@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/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).