Den 20.08.2017 21.28, skrev Bryan Pendleton: > Hmmm... Does this mean that the central Subversion repository is out of > disk space? > > Or does it mean that the local disk on the Jenkins worker machine is out > of disk space?
Hi Bryan, I think it means the Jenkins build slave is out of disk space. I blacklisted the node, kicked off the job and it passed. I also sent an email to [email protected], asking if someone can take of the problem on the node. If I get some feedback, I'll remove the blacklisting. There are still 23 Ubuntu nodes left to serve the job :) Regards, -- Kristian > > bryan > > > ---------- Forwarded message ---------- > From: *Apache Jenkins Server* <[email protected] > <mailto:[email protected]>> > Date: Sun, Aug 20, 2017 at 11:47 AM > Subject: Build failed in Jenkins: Derby-trunk #2500 > To: [email protected] <mailto:[email protected]> > > > See <https://builds.apache.org/job/Derby-trunk/2500/display/redirect > <https://builds.apache.org/job/Derby-trunk/2500/display/redirect>> > > ------------------------------------------ > > Caused: hudson.scm.subversion.UpdaterException: failed to perform svn update > > Retrying after 10 seconds > Updating https://svn.apache.org/repos/asf/db/derby/code/trunk > <https://svn.apache.org/repos/asf/db/derby/code/trunk> at revision > '2017-08-20T18:46:14.204 +0000' > ERROR: Failed to update > https://svn.apache.org/repos/asf/db/derby/code/trunk > <https://svn.apache.org/repos/asf/db/derby/code/trunk> > org.tmatesoft.svn.core.SVNException: svn: E200030: FULL > >
