this is an explicit call for help. We do not seem to be able to keep a nightly OSX buildbot functioning, even one that builds once a week or so and can be made available for major merges/releases would be better than none. If you have a lead to a modern OSX machine that can donate cycles to PyPy, please respond or join on IRC at #pypy Thanks
That would be great! I would think you could hook in as a buildslave, then take the slave offline and bring it back online at your discretion. Once it is online, it would immediately begin building the backed-up scheduled builds, so you would have to go to http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64 and cancel the excess ones (if we don't find a nightly solution before then and leave the scheduler as currently set up). You seem to be able to build already, so you would just need to follow the instructions for setting up a slave here https://bitbucket.org/pypy/buildbot/src/98c105c0aaefe7392d6392ae5ba7f7c5e134... Matti On 22/05/15 16:26, Костя Лопухин wrote:
Hello Matti! I can do weekly builds and tests on weekends or on request (most of the time).
On Fri, May 22, 2015 at 4:18 PM Matti Picus <matti.picus@gmail.com> wrote:
If you have a lead to a modern OSX machine that can donate cycles to PyPy, please respond or join on IRC at #pypy
Will a Hackintosh VM do? I've just finished installing one (with Niresh's Yosemite ISO) and it successfully built PyPy. I'm still to figure out how to better run tests though. It's on my home server that's up almost all time (may hang sometimes or reboot due to power fluctuations) and enough spare RAM (allocated 6G for it) and CPU cycles (packet forwarding will never load up all 4 cores of it). I know that it might be not good enough for producing proper releases, but for nightly tests it should be OK.
That would be great! I would think you could hook in as a buildslave, then take the slave offline and bring it back online at your discretion. Once it is online, it would immediately begin building the backed-up scheduled builds, so you would have to go to http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64 and cancel the excess ones (if we don't find a nightly solution before then and leave the scheduler as currently set up). You seem to be able to build already, so you would just need to follow the instructions for setting up a slave here https://bitbucket.org/pypy/buildbot/src/98c105c0aaefe7392d6392ae5ba7f7c5e134... Matti On 22/05/15 16:26, Костя Лопухин wrote:
Hello Matti! I can do weekly builds and tests on weekends or on request (most of the time).
On Fri, May 22, 2015 at 4:18 PM Matti Picus <matti.picus@gmail.com> wrote:
If you have a lead to a modern OSX machine that can donate cycles to PyPy, please respond or join on IRC at #pypy
Will a Hackintosh VM do? I've just finished installing one (with Niresh's Yosemite ISO) and it successfully built PyPy. I'm still to figure out how to better run tests though. It's on my home server that's up almost all time (may hang sometimes or reboot due to power fluctuations) and enough spare RAM (allocated 6G for it) and CPU cycles (packet forwarding will never load up all 4 cores of it). I know that it might be not good enough for producing proper releases, but for nightly tests it should be OK.
participants (3)
-
Matti Picus -
Yuriy Taraday -
Костя Лопухин