From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10569 invoked by alias); 24 May 2007 17:35:48 -0000 Received: (qmail 10515 invoked by uid 22791); 24 May 2007 17:35:43 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 24 May 2007 17:35:38 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l4OHZaLX007016; Thu, 24 May 2007 13:35:36 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4OHZZi5000577; Thu, 24 May 2007 13:35:35 -0400 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4OHZX8r032516; Thu, 24 May 2007 13:35:34 -0400 Message-ID: <4655CCF6.8080607@redhat.com> Date: Thu, 24 May 2007 19:25:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 1.5.0.10 (X11/20070301) MIME-Version: 1.0 To: Kris Van Hees CC: frysk Subject: Re: Automated build-and-test summary report (2007/05/23) References: <20070523141034.GA16276@ca-server1.us.oracle.com> <46545CB3.6000509@redhat.com> <20070523214658.GB16276@ca-server1.us.oracle.com> In-Reply-To: <20070523214658.GB16276@ca-server1.us.oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00202.txt.bz2 Hi Kris, Is it possible to separate out the building and reporting functions so that there's a weekly summary showing trends? In general, crasher bugs are found quickly and directly by running the test-suite locally. Its the more obscure failures, that are missed by normal testing, and require drilling down through change/build history that are really helped by this system. Andrew Kris Van Hees wrote: > I may be missing something, but I honestly do not understand the issue > here. Obviously, an automated build-and-test system that performs > nightly builds is hardly any use if the results are only emailed out > once a week. The continuing existence of tests that show intermittent > failures, and the continued failure of the dist-builds (that you in fact > suggested be added to the list of configuration) indicates that we (as > developers) are not detecting and reporting all problems. The automated > system is performing a full-scale test, and extracts the relevant output > from the tests, consolidating those in clear reports. > > However, if receiving a daily report in email places an undue burden on > you, I can certainly disable the scheduling of nightly builds for Frysk. > There is no point in running tests when you don't want the results > distributed to the developers. > > Cheers, > Kris > > On Wed, May 23, 2007 at 11:24:35AM -0400, Andrew Cagney wrote: > >> Kris, >> >> Does this really need to be semi-daily? I thought it was happily >> posting weekly summaries. As developers we can more directly detect and >> report immediate problems. >> >> Andrew >> >>