Re: [Monotone-devel] Help request with buildbot for monotone

[Markus Schiltknecht]

Richard Levitte wrote:
> That looks exactly like mine, modulo some name changes ;-)

Hum...

> My master log currently looks like this:
> 2007/07/09 11:12 +0200 [HTTPChannel,15,213.221.101.147] web forcebuild of 
> builder 'i386-debian-testing', branch='', revision=''
> 2007/07/09 11:12 +0200 [HTTPChannel,15,213.221.101.147] maybeStartBuild <Builder 
> 'i386-debian-testing' at -1219213428>: [<buildbot.process.base.BuildRequest instance at 
> 0xb74cb70c>] [<buildbot.process.builder.SlaveBuilder instance at 0xb74c016c>]
> 2007/07/09 11:12 +0200 [HTTPChannel,15,213.221.101.147] <Builder 
> 'i386-debian-testing' at -1219213428>: want to start build, but we don't have a 
> remote

As your buildbot didn't detect any changes, yet, it didn't automatically 
start a build process on the slaves. Thus I've manually tried to force a 
build - which is recorded in the above log lines. The error message 
isn't quite clear, though.

> The slave log file looks like this:
>
> 2007/07/07 19:39 +0200 [Broker,client] message from master: attached
> 2007/07/07 19:39 +0200 [Broker,client] I have a leftover directory 'info' that 
> is not being used by the buildmaster: you can delete it now
> 2007/07/07 19:39 +0200 [Broker,client] 
> SlaveBuilder.remote_print(i386-debian-testing): message from master: attached
> 2007/07/07 19:39 +0200 [Broker,client] sending application-level keepalives 
> every 600 seconds
> 2007/07/07 19:49 +0200 [-] sending app-level keepalive
> [ ... a large bunch of messages, all looking like the last one above ...]
> 2007/07/09 10:19 +0200 [-] sending app-level keepalive
> 2007/07/09 10:25 +0200 [Broker,client] 
> SlaveBuilder.remote_print(i386-debian-testing): message from master: ping
> 2007/07/09 10:25 +0200 [Broker,client] SlaveBuilder.remote_ping(<SlaveBuilder 
> 'i386-debian-testing' at -1218905812>)
> 2007/07/09 10:29 +0200 [-] sending app-level keepalive
> [...]

Looks like the client never tried to build anything ever. But it seems 
to be attached to the server correctly - it responds to pings.


My slave prints a little more information when attaching to the server:

> 2007/07/09 13:56 CEST [-] Loaded.
> 2007/07/09 13:56 CEST [-] Starting factory <buildbot.slave.bot.BotFactory instance 
> at 0xb78d76ac>
> 2007/07/09 13:56 CEST [Broker,client] message from master: attached
> 2007/07/09 13:56 CEST [Broker,client] 
> SlaveBuilder.remote_print(test_slave_name): message from master: attached


The above error message ("we don't have a remote") means that no slave 
is available, i.e. there's no slave with status == IDLE.  The buildbot 
server sets the client's status to ATTACHING on accept(), then requests 
the slave to call 'setMaster()' and to print the 'message from master: 
attached' line. Only after that remote call returns, the server set's 
the client's state to IDLE. At least that's what I can tell from the 
buildbot sources. I'm unclear on why your slave fails to print the 
'message from master: attached'.  Can you simply try restarting the 
slave? What does the slave's .tac file look like? What does your 
master.cfg's c['bots'] look like?

What version of buildbot are you using? I'm on CVS HEAD, but debian 
testing seems quite up to date with 0.7.5 as well, while debian stable 
uses 0.7.4, AFAICT.

Hope that helps.

Markus