#2045: Implicit limit of 1000 builders per slave
----------------------+-----------------------
Reporter: xrg | Owner:
Type: undecided | Status: new
Priority: minor | Milestone: undecided
Version: 0.8.4 | Keywords:
----------------------+-----------------------
It has been noted that when > ~1000 builders are configured for a single
slave, the slave cannot go online.
This /must be/ due to a protocol packet size limit, PB transmission size.
The message noted at logs is:
File ".../site-packages/buildbot-0.8.4_pre_741_g2089c5b-
py2.6.egg/build
bot/process/slavebuilder.py", line 107, in <lambda>
self.remote.callRemote("setMaster", self))
...
File ".../twisted/spread/flavors.py", line 127, in jellyFor
return "remote", jellier.invoker.registerReference(self)
File ".../twisted/spread/pb.py", line 666, in registerReference
raise Error("Maximum PB reference count exceeded.")
twisted.spread.pb.Error: Maximum PB reference count exceeded.
--
Ticket URL: <http://trac.buildbot.net/ticket/2045>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
