[devel at bb.net] Request for more buildbot testing resources between Py3 and Py2

Pierre Tardy tardyp at gmail.com
Mon Oct 2 08:46:22 UTC 2017

Hi Craig,

We already talked about this during the weekly meeting.
This does not make much sense to use nine.buildbot.net to test worker
protocol interop, as it uses buildbot travis, and does not use all the
remote commands that are required to be tested. Also nine.bb.net uses
Hyper, which adds another level of complexity, and we can't have the
stability of this setup slow down other buildbot developement (npm
instabilities are already painful enough)

Your dogfooding proposal is better than nothing, but still requires a lot
of work, and is hard to reproduce if somebody breaks something.

End to end tests are easier, and more controllable, reproducible, etc.

Vladimir Rutsky started one here:
Please feel free to finish his work.

Another option I think is a bit better is to change

So that it does not create a worker inside the master's virtualenv, but to
create a worker in another virtualenv, with the option to use another
Using that method, will allow us to leverage all the integration tests that
we already have, and not to have to create more in Vladimir's framework.


On Thu, Sep 28, 2017 at 2:51 PM Craig Rodrigues <rodrigc at crodrigues.org>

> Hi,
> I submitted this patch:
> https://github.com/buildbot/buildbot/pull/3649
> which fixes interop between:
>  0.9 master (Python 3) <==> 0.9 worker (Python 2)
>  0.9 master (Python 2) <===> 0.9 worker (Python 3)
> Pierre reviewed and merged the patch to the master branch.
> I would like to request more resources for testing buildbot be set up.
> ==========================
> 1.  A buildbot 0.8.x slave running Python 2 to be connected to
>      the nine.buildbot.net master running Python 2.
> 2.  A buildbot 0.9 worker running Python 3 to be connected to
> nine.buildbot.net
> ==============================
> 1.  A new buildbot 0.9 master to be set up running Python 3.
>      For this discussion, I'll call it nine-py3.buildbot.net, but you can
> call it anything. :)
> 2.  One buildbot 0.9 worker running Python 3 to be set up and connected to
> nine-py3.buildbot.net
> 3.  One buildbot 0.9 worker running Python 2 to be set up and connected to
> nine-py3.buildbot.net
> 4.  One buildbot 0.8.x worker running Python 2 to be set up and connected
> to nine-py3.buildbot.net
> Is this doable to set this up?
> This will help with testing Python 3, and help improve confidence that
> things will work and interoperate with different versions of Python.
> --
> Craig
> _______________________________________________
> devel mailing list
> devel at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/devel/attachments/20171002/b5d85c9c/attachment.html>

More information about the devel mailing list