Any volunteers to host a win32 buildbot slave? It would be nice to have at least two machines online, since the processes seem so slow on that platform. The current builder has gotten stuck and the maintainer is not responding to emails, we are down to no functioning buildbot slaves for that platform. Minimum requirements are: - relatively new hardware - at least 8GB memory - 5 GB disk space for pypy (not including OS and visual studio) - internet connection I looked into an Azure vm, but from what I could tell it would be about $10 per translation, and maybe more for an own-tests run, since the machines with significant RAM are expensive. We tried once to get Microsoft to donate some credits, but that did not go far. Matti
On Mon, 24 Apr 2017, Matti Picus wrote:
Any volunteers to host a win32 buildbot slave?
It would be nice to have at least two machines online, since the processes seem so slow on that platform.
The current builder has gotten stuck and the maintainer is not responding to emails, we are down to no functioning buildbot slaves for that platform.
Hi Matti, Sorry for the delay, I've been on a fully offline vacation, and have just opened my inbox (with horror) to find your emails among thousands of others. I'm still travelling, but I will be back home in a couple of days and will have a look into the win32 builder as soon as I get access to my computer... Maybe we should have another go at trying to activate the damn MSDN subscription. The last time I've eventually given up after dozens of emails, as I had few other pressing issues to resolve... -- Sincerely yours, Yury V. Zaytsev
On Sat, 29 Apr 2017, Matti Picus wrote:
Cool, hope you had a good vacation. Looking forward to hearing from you when you get settled.
Yeah, it was pretty awesome, especially the offline aspect ;-) , but sure enough the servers go on strike as soon as I'm AFK, so busy times ahead...
As for MSDN, you have another set of mails about that :), the bottom line is that we have tried Azure, and are waiting for answers from Microsoft how to proceed.
It seems that I wasn't on CC, so would you care to forward relevant stuff if there is anything I could help you with? I think you have everything I had so far, the last state I'm aware of was that the MSDN code was issued, but I couldn't activate it due to an unknown issue with the website, and so we needed to use the official support channel for that, which in the end I didn't get to... -- Sincerely yours, Yury V. Zaytsev
On Sat, 29 Apr 2017, Matti Picus wrote:
Cool, hope you had a good vacation. Looking forward to hearing from you when you get settled.
I've just had a look at the build slave, and it seems that it's the usual problem with Windows sucking in some updates but failing to restart properly or whatever. I did some minor cleanups and it looks like it's running again, but could someone with access to buildbot please restart it? There is a job stuck there that I'm unable to remove no matter what: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/3075 I didn't have a look into updating the libraries yet, but hopefully will get to it sometime this week (?!)... -- Sincerely yours, Yury V. Zaytsev
On Sun, 30 Apr 2017, Matti Picus wrote:
We cannot kill it from the buildbot master side. I'm pretty sure I've seen this before, where hg just hangs, and the only solution is to kill the buildslave process on the win32 machine (which may involve a reboot).
No, the process doesn't exist on the slave, precisely because it has been rebooted multiple times in the mean time, but the master is confused about it and believes that the build is still running. -- Sincerely yours, Yury V. Zaytsev
On 30/04/17 23:14, Yury V. Zaytsev wrote:
On Sun, 30 Apr 2017, Matti Picus wrote:
We cannot kill it from the buildbot master side. I'm pretty sure I've seen this before, where hg just hangs, and the only solution is to kill the buildslave process on the win32 machine (which may involve a reboot).
No, the process doesn't exist on the slave, precisely because it has been rebooted multiple times in the mean time, but the master is confused about it and believes that the build is still running.
My bad, restarting the build master seems to have stopped that job. Before nightlies run you may want to check that "hg pull" can run in that directory c:\pypy\buildbot\pypy-c-jit-win-x86-32\build
participants (2)
-
Matti Picus -
Yury V. Zaytsev