[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: New buildbot slave - Centos

From: Dave Brown <dave.brown_at_wandisco.com>
Date: Sun, 15 Nov 2009 17:05:48 -0800

Lieven Govaerts wrote:
> On Sun, Nov 15, 2009 at 2:12 AM, Dave Brown <dave.brown_at_wandisco.com> wrote:
>> Lieven Govaerts wrote:
>>> On Sat, Nov 14, 2009 at 1:40 AM, Julian Foad <julian.foad_at_wandisco.com>
>>> wrote:
>>>> Lieven Govaerts wrote:
>>>>> Indeed, in the buildslave basedir info/host and info/admin files. See
>>>>> step 8 in the manual:
>>>>> http://djmitche.github.com/buildbot/docs/0.7.11/#Creating-a-buildslave
>>>> Ah, the manual! That was what I needed. Thanks, Lieven.
>>>> I have run the appropriate "buildbot create-slave" command and edited
>>>> the info files. Dave is taking over now. He has to install a few more
>>>> buildbot dependencies, I think, before it will run properly, as well as
>>>> figure out how to tell it how to find and run our "svnbuild.sh" etc.
>>>> scripts, and make it actually connect to your machine (if it isn't
>>>> already trying). I passed Dave the connection info that you emailed me.
>>> I've restarted the buildbot master, it's now ready to accept your build
>>> slave.
>>> If you start up the slave with the info I've sent you, it will connect
>>> to the master. On the first connection it will automatically create a
>>> new directory x64-centos in the base directory.
>>> The working copy will be put in the BASEDIR/x64-centos/build
>>> directory, which is considered as cwd. So if you put the scripts in
>>> BASEDIR/x64-centos, the master will find them there.
>>> Lieven
>> The CentOS bot is alive and kicking. It's running davautocheck for the core
>> tests, and javaHL, python-swig, and perl binding tests. Some python
>> libraries had to be installed manually, since CentOS packages don't deliver
>> everything, but they're listed in the info/host file.
> So you're running ra_serf tests then? The master is actually passing a
> string to the svn-check script specifying which ra layer is used for
> testing. The scripts don't use these (yet), so we do it the other way
> around. I make sure the string passed by the master matches with what
> the slave is checking. This way the waterfall page shows the correct
> info.

This machine is using ra_neon. I can do neon and/or serf if that fills
more holes in coverage. But I notice that your OS X machine is doing
ra_serf already. There are currently no libserf rpm's in the default
CentOS repositories, and it seems most sensible to mimic what the
package maintainers for a given platform are likely to use. So I'm
assuming CentOS will use ra_neon, unless they pull in serf officially
when 1.7 comes down. There are 3rd party repositories that currently
have libserf, or else I can just build from source.


> ..
>> Lieven, unless you see anything wrong, you can make it fully live at your
>> leisure.
> Well, the repository is not online now, and I won't be at my PC for
> the next 18hrs, so I'll make the switch then.
> thanks.
> Lieven

Received on 2009-11-16 02:06:01 CET

This is an archived mail posted to the Subversion Dev mailing list.