Community
Participate
Working Groups
I cleaned up my builds on Friday so they aren't the ones consuming all the space. Perhaps all projects should be encouraged to configure hudson so the builds are deleted after five builds or something like that :-)
Kim can you help me understand how you've determined all this? Both slaves are listed, and when I use the Hudson Script Console on each of slave1 and slave2, I get a successful execution. Disk space on neither of those is full.
From slave 2 https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-equinox-test-N/210/console look for no space left on device for slave1 I got a time out and fail to determine https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-equinox-test-N/209/console Started by user kmoir Building remotely on hudson-slave2 [eclipse-equinox-test-N] $ cvs -Q -z3 -d :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse co -P -D "Monday, November 15, 2010 9:09:38 PM UTC" org.eclipse.releng org.eclipse.releng.eclipsebuilder hudson.util.IOException2: remote file operation failed: <https://hudson.eclipse.org/hudson/job/eclipse-equinox-test-N/ws/> at hudson.remoting.Channel@3af64389:hudson-slave2 at hudson.FilePath.act(FilePath.java:749) at hudson.FilePath.act(FilePath.java:735) at hudson.scm.CVSSCM.checkout(CVSSCM.java:374) at hudson.model.AbstractProject.checkout(AbstractProject.java:1061) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) at hudson.model.Run.run(Run.java:1273) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:129) Caused by: java.io.IOException: Remote call on hudson-slave2 failed at hudson.remoting.Channel.call(Channel.java:566) at hudson.FilePath.act(FilePath.java:742) ... 9 more
I'm writing a few scripts that will report all the Hudson disk usage to cross-project once a week.
> look for > > no space left on device I believe that is on dev.eclipse.org. pserver seems to copy everything to /tmp before sending it out on the wire, and we're running out of inodes. If you're using the cvs command directly, you'd be better served with :local:/cvsroot/eclipse instead of pserver.
We've resolved these disk space issues.