[haiku-commits] Re: buildbot failure in HAIKU on (whole buildset)

  • From: Urias McCullough <umccullough@xxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Wed, 8 Apr 2015 14:40:01 -0700

On Tue, Apr 7, 2015 at 4:10 AM, Art <art@xxxxxxxxxxxxxx> wrote:

Am 31/03/2015 um 14:17 schrieb buildbot@xxxxxxxxxxxx:
Buildslave for this Build: arfonzo-bot1-debian

My changes require cURL 7.32.0 -- that version is now almost 2 years
old, so I did not expect to get into troubles here. Obviously, I did not
notice we have a Debian build bot :-)
What shall we do now?

Unfortunately, I have decided to stop my buildslave for now due to a lack of
time to properly resolve this with Debian (stable). Unless someone has
further recommendations, I will be building a new Ubuntu VM with similar
resources (16 cores, 16 GB RAM) in the upcoming month, and migrating the
buildslave over.

I believe the best thing to do is to avoid using Debian (stable), perhaps
until Jessie becomes the new stable. We should probably document this
somewhere for those interested in hosting buildslaves.

Some of my slaves are running LMDE (linux mint debian edition - uses
semi-rolling debian testing as the base)...and last I checked, the
device tree compiler still wasn't updated on that version making those
slaves somewhat useless as well.

I'll see what I can do about bringing some of the slaves here up to
date and getting them online again - but my time has been pretty thin
the last couple months.

In the meantime, if you see some of my slaves failing - it's probably
cuz I'm bringing them online to see what works/doesn't work currently.

- Urias

Other related posts: