> On 21 Aug 2017, at 6:45 am, Kristian Waagan <[email protected]> wrote: > > Hi, > > It looks like the Jenkins build slave qnode3.quenda.co has some kind of > problem, maybe a full disk, a hung process or permission issues. The log > is full of failed attempts to delete files on /tmp, and the Derby build > I was troubleshooting failed because of a failed svn update (E200030: FULL) > > I don't know who handles these nodes. Can someone take care of this, or > point me in the right direction? > If nothing else, maybe a Jenkins admin can disable the node?
Node is inaccessible, I’ll notify upstream providers to take a look. In the meantime I’ve taken it offline. HTH Gav… > > > Thanks, > -- > Kristian
