public inbox for
 help / color / mirror / Atom feed
From: Kris Van Hees <>
To: Mark Wielaard <>
Cc: Elena Zannoni <>,
Subject: Re: Again the build is broken :(
Date: Fri, 24 Aug 2007 16:44:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Aug 24, 2007 at 04:38:48PM +0200, Mark Wielaard wrote:
> I am personally using Fedora Core 6 (x86_64) as main development
> platform and test everything (quickly) on Fedora 7 (x86) before
> committing. But I guess other people have other platforms available. I
> do appreciate the autobuilder Kris setup since that shows some more
> platforms. Maybe we can change it a little to better show which patch
> breaks what on which platform, but that would mean actually building
> each commit, which might be a little too much for the system.

Actually, we could get fairly close to a per-commit building if we could get
the build process that frysk uses a bit more streamlined.  That might involve
quite a bit of work though, and someone will need to be given the cycles to do
it.  Even without a per-commit build it is possible to report on changes that
occured between two builds (and in fact, the web site currently provides all
anyone needs to do that already - the <blah>.rev files contain both a
date/time stamp of the checkout/update and a list of the exact CVS reivision
IDs, so comparing two you get an exact list of what files changed and what the
source and target revisions are per file).

Fortunately, it has almost always been extremely obvious what broke the build,
even wth just daily builds.  So, it may not be that big of a problem to solve
right now.

The ultimate problem remains though...  no one has made any contribution to
the autobuild system, and the one promise to contribute running builds never
happened.  There are limitations to how much can be done in reasonable time
without builds being contributed.


  parent reply	other threads:[~2007-08-24 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  5:51 Kris Van Hees
2007-08-24  8:16 ` Mark Wielaard
2007-08-24 11:12   ` Mark Wielaard
2007-08-24 11:47     ` Mark Wielaard
2007-08-24 12:34   ` Andrew Cagney
2007-08-24 14:26     ` Elena Zannoni
2007-08-24 14:39       ` Mark Wielaard
2007-08-24 15:17         ` Phil Muldoon
2007-08-24 16:14           ` Elena Zannoni
2007-08-24 21:00             ` Andrew Cagney
2007-08-28  0:19             ` Phil Muldoon
2007-08-24 16:44         ` Kris Van Hees [this message]
2007-08-26 21:21 Kris Van Hees

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).