[Python-buildbots] The process of adding my buildbot worker to the buildbot fleet
Hi, Experts: I want to add a new platform support for cpython, that is VxWorks RTOS. A builtbot worker has been internally setup ready to join the fleet. But any process or guidance I need to follow? Where is the master.cfg located? And who and how to modify that? I checked the source code repo but no any file called master.cfg there. Thanks, Peixing ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Re: [Python-buildbots] The process of adding my buildbot worker to the buildbot fleet
Hi Peixing, On Thu, Feb 21, 2019 at 7:23 AM Xin, Peixing wrote: > I want to add a new platform support for cpython, that is VxWorks RTOS. A > builtbot worker has been internally setup ready to join the fleet. But any > process or guidance I need to follow? Where is the master.cfg located? And > who and how to modify that? I checked the source code repo but no any file > called master.cfg there. The buildbot master configuration can be found here: https://github.com/python/buildmaster-config/tree/master/master, please feel free to open a pull request there adding your builder(s). Once we're ready to merge that, I'll contact you privately with credentials to connect. -- Zach ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
[Python-buildbots] Any advice for the good "size" of a Python buildbot worker?
Hi, We would like to add more buildbot workers for test Python on Fedora and RHEL, but I have no idea of the ideal "size" of a worker: * Number of CPUs? I guess that 2 CPUs is nice but 4 or more is better? * Memory size? At least 8 GB? * Minimum storage? Logs are sent to the buildbot server, so there is no much stored for long term, no? On my laptop, my python source directory takes around 500 MiB including ".git" repository and object files (.o, .so, python binary, etc.) with Python compiled in debug mode (keep debug symbols) I would say that 10 GiB is nice, 20 GiB is better? Victor -- Night gathers, and now my watch begins. It shall not end until my death. ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Re: [Python-buildbots] Any advice for the good "size" of a Python buildbot worker?
On Thu, Feb 21, 2019 at 8:06 AM Victor Stinner wrote: > We would like to add more buildbot workers for test Python on Fedora > and RHEL, but I have no idea of the ideal "size" of a worker: It basically comes down to how long you want to wait for results :). The devguide lists [1] 2 cpu, 512 MB RAM and 30GB storage as the preferred minimums, but that may or may not actually be enough anymore, especially on RAM. For reference, here are stats on my workers (formatting may be destroyed by Gmail, sorry if so): +-+ | | Type | CPU | RAM | Disk (GB) | | | | cores | threads | freq (GHz) | (GB) | Total | Free | +-+ | ware-gentoo-x86 | Bare metal| 2 | 2 | 2.6 | 2 | 52 | 37 | | ware-alpine | Docker on physical| 4 | 8 | 3.4-3.9 | 16| 108| 66 | | ware-win81-release | Azure VM | 2 | 2 | 2.39 | 14| 100| 91 | +-+ [1] https://devguide.python.org/buildworker/#required-resources -- Zach ___ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
