[haiku-development] Re: 64bit build broken, again

  • From: Ingo Weinhold <ingo_weinhold@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 15 Sep 2014 12:22:03 +0200

On 15.09.2014 09:23, anders williamson wrote:

People keep telling me that. I'm aware. It's not the point. The point
is to make sure people build their stuff before pushing. Especially
if pushing is the last thing you do before going to bed or on
vacation. There are no excuses.
Please calm down. Yes, building and testing a change before committing it is the standard procedure and not doing so is frowned upon. However, should you ever become a frequent contributor, you'll realize that something can slip by on a rare occasion. As Axel wrote, we're only human. There's certainly no need to feel personally offended because someone broke "your build".
If you want to keep your clone in sync and at the same time have the guarantee that things build, simply update only to a revision that already went successfully through CI. You generally won't be more than a few minutes behind the head revision. 


If the build breaks for an arch you don't have access to, then that's
different, but that's clearly not the case here.

>

(tip: check that you've built in a pre-push hook, and have the hook
build if necessary)
Since cross-compiling is possible for every supported architecture, that would be a horrible waste of time. We have a noisy CI exactly so that one doesn't have to build every change for all architectures. 

CU, Ingo

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 09-2014