I hate to be the bearer of bad news, but the buildbot appears to still be hung 
up … no new docs, etc.  

Is there a way to maybe skip all the previous builds that may have caused it 
angst until Andy committed the one release that fixed the po4a problem?  Of 
course I don’t know what the problem is so I’m just thinking out loud.

Thanks!!

-Greg

> On Sep 16, 2024, at 10:31 PM, Sebastian Kuzminsky <s...@highlab.com> wrote:
> 
> buildbot2 had crashed, the buildbot process itself was killed by the
> out-of-memory killer.  The docs are built by buildbot2, so this explains
> why they haven't been updating.
> 
> (Maybe a memory leak in the buildbot process, or maybe i just
> under-provisioned that VM?  I was at 2 GB RAM, i bumped it up to 4 GB,
> which exhausts the memory on the VM host...)
> 
> I restarted it and builds have started up again, hopefully there will be
> fresh docs in a few hours (lots of builds to get through).
> 
> 
> If we *can* move the docs builder to github, that might be a good idea.
> I'm a bit worried since the docs builder currently has an ssh key that
> allows it to rsync the docs to www.linuxcnc.org, and we'd have to be
> careful if we put that key on github somewhere.  Or to come up with some
> other way to deliver the docs.
> 
> Or just host the built docs on github, though i've always taken it as a
> point of pride that we're mostly self hosting.  But clearly i don't have
> the energy to do a good job of it any more.
> 
> --
> Sebastian Kuzminsky
> 
> 
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to