From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: RFC: libc-testresults mailing list
Date: Wed, 02 Nov 2016 16:48:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611021639370.18772@digraph.polyomino.org.uk> (raw)
In-Reply-To: <df1d2a90-bf16-87e9-a14a-02c73051fe14@redhat.com>
On Wed, 2 Nov 2016, Carlos O'Donell wrote:
> Do we expect that libc-testresults is a superset of those builds we have
> connected to our buildbot CI infrastructure?
>
> Do we expect buildbot test results to go to libc-testresults for archiving?
If we add a script to mail out results then I think it would be
appropriate to make our buildbot scripts use it (having made sure that
existing buildbot instances have working outgoing mail and documented that
as a requirement for buildbot instances). In that case, yes, it would be
a superset of the buildbot builds (note Andrew was asking about where to
send results from a system not hooked up to our buildbot).
We can consider questions such as how much goes in test results mails from
such a script, e.g. do we include the full tests.sum (possibly gzipped and
attached) or just results that aren't PASS, what standard information
about the test environment goes in mails, whether to attach (gzipped) .out
files of failing tests if they aren't too many / too big, how mails should
declare that they are the standard output of the script to allow for
automatic parsing.
It would of course be expected that if someone's build system starts
flooding the list with multiple mails from identical builds (keeping
rebuilding the same versions continuously, or mail system problems
resulting in duplicate mails) then those mails would be blocked until the
problem is sorted out.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-02 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 13:06 Joseph Myers
2016-11-02 14:30 ` Carlos O'Donell
2016-11-02 16:48 ` Joseph Myers [this message]
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.1611021639370.18772@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.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).