public inbox for
 help / color / mirror / Atom feed
From: Phil Muldoon <>
To: Elena Zannoni <>
Cc: Mark Wielaard <>,
Subject: Re: Again the build is broken :(
Date: Tue, 28 Aug 2007 00:19:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Elena Zannoni wrote:
> Sure, the two things you mention are not mutually exclusive.
> However there is a cost to identifying broken builds too, and it seems 
> that Mark is drawing the
> short straw frequently, since he is usually the first to correct said 
> oversights. It takes away some
> of his time from development. 

I'll segway into distributed version control here, my favorite pet topic 
;) It's great for isolating people from other peoples commits, and the 
ability to locally remove (or re-pull) whatever patch-sets you like. 
This a good thing, if a patch is bothering you then remove that 
change-set, then pull it later when it is mixed.

OTOH I think we all try to keep a stable CVS HEAD, but sometimes things 
just slip. Anyway, old ground there but ...
> What I have suggested is that, like we used to do once upon a time, we
> stick with as few development platforms as we can get away with in 
> order to minimize the
> oversights. So if the platforms supported are FC6 and F7, let's stick 
> with those and make
> everybody's life easier. If somebody wants to add FC5 to the test 
> grid, please do so and contribute
> the tests results so that they can be uploaded. Any takers?

I don't think the platforms have changed much since the time you talk 
about. But then again, there are other concerns now and in the future 
for other growth platforms. We have a Debian package now that Thomas 
works on. Mike is/was working on a Gentoo version. Fedora, RHEL and 
other distros. The math gets scary when you take platforms * 
architectures. Add into that the changing dynamics of the kernel across 
those platforms, and the only sane way to keep track of these is a build 

Ideally, in a hardware rich world I'd like to submit a job to a build 
farm so it could lint all this automatically. Especially when I work on 
CNI code. I don't see the build farm failing as a "failure" but rather 
"doing its job".



  parent reply	other threads:[~2007-08-28  0:19 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 [this message]
2007-08-24 16:44         ` Kris Van Hees
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).