Has this problem been resoved? People are getting buildslaves on python.org for other things, so I suspect we could have one if we just asked. Laura (who doesn't want to ask if the problem has been already solved.)
While the specific linux64 problem has been resolved, we have lost our windows buildbot (it ran as a virtual machine on allegro64) as well as our only fully functional macosx buildbot. Anyone who can pull some strings to obtain buildslaves is more than welcome to do so. I am willing to be the POC for the windows buildslave once a suitable machine is located that can run it or can host a virtual machine that can run it. We need ~4GB RAM and at least 20GB disk space, the builds run about 7 hours on a single CPU core. Matti On 21/04/15 22:47, Laura Creighton wrote:
On Wed, 2015-04-22 at 12:37 +0300, Matti Picus wrote:
Hi Matti, What are the requirements for the Windows build slave? I have a machine with >4G RAM and >20G disk running Windows 7 x86_64 that I use as a builder for my hobby projects. I can't provide direct root ssh access to it though, as it's in a firewalled environment, is that a problem? Another catch is that I'm not sure about the longterm future of this box, but I would expect at least ~4-6 months lifetime, and if it's going to be decommissioned, I'll try to find a replacement. -- Sincerely yours, Yury V. Zaytsev
On 22/04/15 23:05, Yury V. Zaytsev wrote:
Thanks for the offer. You can set up the buildslave yourself, no need to give anyone else access to the box. The buildslave would run as a process that would talk to the buildmaster over a TCP socket, so being behind a firewall should not be a problem as long as the port from the slave to the master is open. We run nightly tests that can be scheduled to your convenience, they requre about 7-8 hours of CPU time total. Some of the tests can be run in parallel, two cores will run the tests in about 5 hours of wall-clock time, YMMV. You need to be able to build ppy, directions are here http://doc.pypy.org/en/latest/windows.html To set up a buildslave, read this https://bitbucket.org/pypy/buildbot/src/default/README_BUILDSLAVE and then come join us on IRC at #pypy so we can update the buildmaster with your details Matti
On Wed, 2015-04-22 at 12:37 +0300, Matti Picus wrote:
Okay, sorry guys, but it seems that in my attempts to fix the compiler detection that wasn't working, I somehow got the master to get stuck by rebooting the slave at an unfortunate moment (this build doesn't react to "Stop build" anymore): http://buildbot.pypy.org/builders/own-win-x86-32/builds/504 I would appreciate if you could restart the master or otherwise recover from this, but it seems that there is noone on IRC who can do this now. The compiler detection should now work by the way, but I can't check, because of this stuck build. -- Sincerely yours, Yury V. Zaytsev
Hi, On 25 April 2015 at 01:32, Maciej Fijalkowski <fijall@gmail.com> wrote:
This can be resolved on the slave level, not on master level
Yes, you can stop (disconnect) the slave, and then restart it. I never really understood the "Stop" buttons on the buildbot web pages, because some of them seem to have no effect, or only sometimes. A bientôt, Armin.
On Sat, 2015-04-25 at 08:41 +0200, Armin Rigo wrote:
So how do I do that? I have already tried stopping buildbot service and then starting it again, and this didn't change anything. I'm confused about your terminology: I can't see a button saying "Disconnect" anywhere. When I stopped the buildbot service, the slave appeared disconnected on the buildbot pages. Is that what you meant? Just to make it clear: the build is not actually running on the slave anymore and the slave reports that it's idle. It's just that the master for some reason disagrees. -- Sincerely yours, Yury V. Zaytsev
While the specific linux64 problem has been resolved, we have lost our windows buildbot (it ran as a virtual machine on allegro64) as well as our only fully functional macosx buildbot. Anyone who can pull some strings to obtain buildslaves is more than welcome to do so. I am willing to be the POC for the windows buildslave once a suitable machine is located that can run it or can host a virtual machine that can run it. We need ~4GB RAM and at least 20GB disk space, the builds run about 7 hours on a single CPU core. Matti On 21/04/15 22:47, Laura Creighton wrote:
On Wed, 2015-04-22 at 12:37 +0300, Matti Picus wrote:
Hi Matti, What are the requirements for the Windows build slave? I have a machine with >4G RAM and >20G disk running Windows 7 x86_64 that I use as a builder for my hobby projects. I can't provide direct root ssh access to it though, as it's in a firewalled environment, is that a problem? Another catch is that I'm not sure about the longterm future of this box, but I would expect at least ~4-6 months lifetime, and if it's going to be decommissioned, I'll try to find a replacement. -- Sincerely yours, Yury V. Zaytsev
On 22/04/15 23:05, Yury V. Zaytsev wrote:
Thanks for the offer. You can set up the buildslave yourself, no need to give anyone else access to the box. The buildslave would run as a process that would talk to the buildmaster over a TCP socket, so being behind a firewall should not be a problem as long as the port from the slave to the master is open. We run nightly tests that can be scheduled to your convenience, they requre about 7-8 hours of CPU time total. Some of the tests can be run in parallel, two cores will run the tests in about 5 hours of wall-clock time, YMMV. You need to be able to build ppy, directions are here http://doc.pypy.org/en/latest/windows.html To set up a buildslave, read this https://bitbucket.org/pypy/buildbot/src/default/README_BUILDSLAVE and then come join us on IRC at #pypy so we can update the buildmaster with your details Matti
On Wed, 2015-04-22 at 12:37 +0300, Matti Picus wrote:
Okay, sorry guys, but it seems that in my attempts to fix the compiler detection that wasn't working, I somehow got the master to get stuck by rebooting the slave at an unfortunate moment (this build doesn't react to "Stop build" anymore): http://buildbot.pypy.org/builders/own-win-x86-32/builds/504 I would appreciate if you could restart the master or otherwise recover from this, but it seems that there is noone on IRC who can do this now. The compiler detection should now work by the way, but I can't check, because of this stuck build. -- Sincerely yours, Yury V. Zaytsev
Hi, On 25 April 2015 at 01:32, Maciej Fijalkowski <fijall@gmail.com> wrote:
This can be resolved on the slave level, not on master level
Yes, you can stop (disconnect) the slave, and then restart it. I never really understood the "Stop" buttons on the buildbot web pages, because some of them seem to have no effect, or only sometimes. A bientôt, Armin.
On Sat, 2015-04-25 at 08:41 +0200, Armin Rigo wrote:
So how do I do that? I have already tried stopping buildbot service and then starting it again, and this didn't change anything. I'm confused about your terminology: I can't see a button saying "Disconnect" anywhere. When I stopped the buildbot service, the slave appeared disconnected on the buildbot pages. Is that what you meant? Just to make it clear: the build is not actually running on the slave anymore and the slave reports that it's idle. It's just that the master for some reason disagrees. -- Sincerely yours, Yury V. Zaytsev
participants (5)
-
Armin Rigo -
Laura Creighton -
Maciej Fijalkowski -
Matti Picus -
Yury V. Zaytsev