From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29745 invoked by alias); 2 Nov 2016 16:48:32 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 28808 invoked by uid 89); 2 Nov 2016 16:48:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=mails, hooked, instances, archiving X-HELO: relay1.mentorg.com Date: Wed, 02 Nov 2016 16:48:00 -0000 From: Joseph Myers To: Carlos O'Donell CC: Subject: Re: RFC: libc-testresults mailing list In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-11/txt/msg00066.txt.bz2 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