[Buildbot-commits] [Buildbot] #68: New mechanism for monitoring buildbot startup

[Buildbot trac]

#68: New mechanism for monitoring buildbot startup
--------------------+-------------------------
Reporter:  joduinn  |       Owner:  tom.prince
    Type:  defect   |      Status:  closed
Priority:  major    |   Milestone:  0.8.9
 Version:  0.7.5    |  Resolution:  fixed
Keywords:  sprint   |
--------------------+-------------------------
Changes (by Jc2k):

 * status:  assigned => closed
 * resolution:   => fixed


Old description:

> The buildbot slave default timeout can be too short for us. Sometimes,
> 5sec isnt always enough, and we get following:
>
> % cltbld$ buildbot start /Users/cltbld/macosx-slave1
>  Following twistd.log until startup finished..
>  The buildmaster took more than 5 seconds to start, so we were unable to
>  confirm that it started correctly. Please 'tail twistd.log' and look for
> a
>  line that says 'configuration update complete' to verify correct
> startup.
> %
>
> ... even though slave started "normally", responds fine to pings from
> buildbot master, and does handle jobs just fine.

New description:

 The buildbot slave default timeout can be too short for us. Sometimes,
 5sec isnt always enough, and we get following:

 % cltbld$ buildbot start /Users/cltbld/macosx-slave1
  Following twistd.log until startup finished..
  The buildmaster took more than 5 seconds to start, so we were unable to
  confirm that it started correctly. Please 'tail twistd.log' and look for
 a
  line that says 'configuration update complete' to verify correct startup.
 %

 ... even though slave started "normally", responds fine to pings from
 buildbot master, and does handle jobs just fine.

--

Comment:

 A different mechanism (that monitors the log rather than using an IPC
 channel) was implemented in master so we are closing this.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/68#comment:16>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation