From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 407 invoked by alias); 20 Mar 2007 14:50:35 -0000 Received: (qmail 398 invoked by uid 22791); 20 Mar 2007 14:50:34 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,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; Tue, 20 Mar 2007 14:50:31 +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 l2KEoIaW013959; Tue, 20 Mar 2007 10:50:18 -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 l2KEoIJY016465; Tue, 20 Mar 2007 10:50:18 -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 l2KEoH7d027901; Tue, 20 Mar 2007 10:50:17 -0400 Message-ID: <45FFF4A3.8000204@redhat.com> Date: Tue, 20 Mar 2007 14:50: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: Observation + advance warning References: <20070320114500.GA11990@ca-server1.us.oracle.com> In-Reply-To: <20070320114500.GA11990@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-q1/txt/msg00234.txt.bz2 Kris, I'm guessing that the, at present, the snapshot date/time is determined by when ever the corresponding CVS commands are run. Unfortunatly that means that it is impossible for anyone to reproduce a test run :-( Can the scripts be modified to specify << -D YYYY-MM-DD-gmt >>, i.e., midnight GMT, as the checkout/update date? The alternative would be to use tags, I don't think that is realistic. Of course the tests can be run several hours after midnight GMT - "in the local wee hours" so to speak. The chance of someone actually committing across GMT is very very low, having implemented a number of snapshot/build systems, I've never seen it as a problem. Andrew (version.in updates slightly before midnight gmt so that it is correct) Kris Van Hees wrote: > Last night's automated build-and-test run was the first of its kind in > that the build actually failed due to CVS' limitations, i.e. being > unable to guarantee atomic commits. As such, it looks like the > automated build was updating its tree at about the same time as Chris > Moller commiting the test for kernel buf 232837. The result was that > the incremental update tree contained the Makefile.am from the commit > but not the kernel232837 directory with the actual test case. > Obviously, this broke the build. > > There isn't really any good solution to this problem in terms of CVS, > since we obviously wouldn't want to do a full lock on the tree for the > purpose of doing build-and-test run checkouts and update. As such, be > forewarned that we're going to have days where the build will be > reported as failing without there really being a mistake on anyone's > part. > > I'll kick off a manual run this morning, and post those results in lieu > of last night's results. > > Cheers, > Kris >