On 08/02/17 17:06, Jesus Cea wrote:
On 08/02/17 16:18, Jesus Cea wrote:
I am trying to convince him to launch buildbot process tree with an "ulimit" to protect the machine. Lets see.
Sorry. Thanks for your patience.
I am launching now the buildbot with a limit of 1GB *PER PROCESS*. At least, when the memory skyrockets it will die without impacting the rest of the machine. Unless it does a fork-bomb...
Backlog is huge. That will be useful to stress the buildbot and, hopefuly, make it fails faster.
Checking the mailing list archives, I am seen Openindiana buildbot memory issues since 2011, at least. <https://mail.python.org/pipermail//python-dev/2011-September/113532.html>. It was never triaged. I am getting mercurial errors because some incompatibility with current release <http://buildbot.python.org/all/builders/x86%20OpenIndiana%203.5/builds/79/steps/touch/logs/stdio>. Since we are moving to github in a couple of days, I will wait until that time to keep pursuing this. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz