From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31154 invoked by alias); 6 Nov 2007 13:45:45 -0000 Received: (qmail 31145 invoked by uid 22791); 6 Nov 2007 13:45:45 -0000 X-Spam-Status: No, hits=-0.0 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org Received: from agminet01.oracle.com (HELO agminet01.oracle.com) (141.146.126.228) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Nov 2007 13:45:39 +0000 Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id lA6DjY4G010038; Tue, 6 Nov 2007 07:45:34 -0600 Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id lA6DjYju016227; Tue, 6 Nov 2007 06:45:34 -0700 Received: from alchar.org by acsmt359.oracle.com with ESMTP id 5625025141194356688; Tue, 06 Nov 2007 07:44:48 -0600 Date: Tue, 06 Nov 2007 13:45:00 -0000 From: Kris Van Hees To: Mark Wielaard Cc: Kris Van Hees , frysk@sourceware.org Subject: Re: Automated build-and-test summary report (2007/11/05) Message-ID: <20071106134446.GE10486@oracle.com> References: <20071105140036.GA2015@oracle.com> <1194344729.3855.1.camel@dijkstra.wildebeest.org> <20071106114115.GD10486@oracle.com> <1194351776.3855.31.camel@dijkstra.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1194351776.3855.31.camel@dijkstra.wildebeest.org> User-Agent: Mutt/1.5.16 (2007-06-09) X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE 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-q4/txt/msg00106.txt.bz2 On Tue, Nov 06, 2007 at 01:22:56PM +0100, Mark Wielaard wrote: > OK, so "First failure: no changes - not built" actually means that the > sources didn't change from the last time the builder ran and so it > wasn't build. Correct? If so the "First Failure" part confused me. Yes, in the email report the first failure entry actually gives the first stage in the build-and-run instance where a failure was detected. There are actually three possible entry types here (both for the current result and for the previous result): - no failures: this obviously is a rare entry, because it means that all stages completed without any problem - no changes - not built: this is reported when there were not changes found in the source tree during the build-and-test run; labrat doesn't perform a build/test run unless at least something in the source tree changed - a stage name: the most common case, reporting the first stage that failed I guess it can be a bit confusing in cases like: First failure: test (was no changes - not built) especially because it might (incorrectly0 read as if the (was...) part is actually an explanation of why 'test' was the first failure, rather than reflecting the previous state (result of the previous build we're comparing to). Would it be more clear if I changed that to be: First failure: test (previously: no changes - not built) > > The fact that the (usually) downloadable logs are not being shown as links > > (that section is empty) is a bug. I'll send notice when it is resolved. > > OK, yes, that was the other confusion. Being worked on right now. The nice part of task separation is that one thing failing in the reporting engine won't stop the rest from work. The less nice part of task separation is that if one thing in the reporting engine fails and the rest keeps working, it is not necessarily noticed (by me) that there is a problem :) Win a few, lose a few. Cheers, Kris