Both actually. Infra bounced the servers and then everything on the queue started to execute.
I’ve ended up stopping everything that was queued since it would take forever to finish, plus multiple builds on the same branch because of multiple commits. For reference I was able to stop the jobs using the tomes-bot in IRC with: stop build tomee-trunk-ubuntu-jvm8 restart or stop build <which> <reason> - Stop a running build Cheers, Roberto > On 4 Dec 2018, at 11:44, Jonathan Gallimore <[email protected]> > wrote: > > Thanks Roberto. What was the fix - did it require infra intervention, or > did you manage to stop the jobs? > > Jon > > On Tue, Dec 4, 2018 at 11:33 AM Roberto Cortez <[email protected]> > wrote: > >> It is up again. >> >> I’ve cancelled all pending builds on the queue and manually started a new >> one: >> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/902 < >> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/902> >> >> Cheers, >> Roberto >> >>> On 4 Dec 2018, at 10:52, Roberto Cortez <[email protected]> >> wrote: >>> >>> Hi folks, >>> >>> TomEE Buildbot seems to be down. I’ve already opened a ticket to Apache >> Infra to see what is going on. It seems that the buildslave is offline. For >> reference: >>> >>> TomEE Build: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 < >> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> >>> Ticket: https://issues.apache.org/jira/browse/INFRA-17357 < >> https://issues.apache.org/jira/browse/INFRA-17357> >>> >>> Also, we were not able to have a successful build since the end of >> October. The current status is unknown until we get the Buildbot up again. >>> >>> Cheers, >>> Roberto >> >>
