public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: Observation + advance warning
Date: Tue, 20 Mar 2007 14:50:00 -0000	[thread overview]
Message-ID: <45FFF4A3.8000204@redhat.com> (raw)
In-Reply-To: <20070320114500.GA11990@ca-server1.us.oracle.com>

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
>   

      reply	other threads:[~2007-03-20 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 11:45 Kris Van Hees
2007-03-20 14:50 ` Andrew Cagney [this message]

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=45FFF4A3.8000204@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=kris.van.hees@oracle.com \
    /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).