The “gcc-debian” and “stable-gcc-debian” builders on @jwe’s buildbots seem to have stopped working.
Is this intentional?
Afaict, most(?) of the Octave developers work with Debian or Ubuntu and with gcc. So, we’d probably notice anyway if something went wrong on that platform and compiler. But it might still be good to have changes checked by those builders.
No, not intentional. I’m not sure what happened this time, but the buildbot service on one of the systems was in the “masked” state where it won’t start. Anyway, I fixed that and restarted it.
It looks like most of the builders on @jwe’s buildbot farm have stopped triggering. I can still see the web interface. But the only builder that seems to be triggering on an update of the default branch is clang-debian. The gcc and Fedora builders don’t seem to trigger.
Was there any change recently?
I found one of my systems powered off this morning. It happened to the other one last week(?). I’m not sure why. After restarting everything seems normal again.
When I saw your message last night I checked and the buildbot workers were not running on either of my buildbot systems. I’m not sure what caused them to stop. I restarted them and things appear to be working normally again.