Hi guys,
We've been getting a lot of Jenkins build failures the last couple of weeks. I didn't set these up (one of our other PMC members did), but seems like we're often (but not always) out of space.... So, is there a way to check disk usage? Should we be scheduling these jobs at a different time to avoid collisions with other builds that might also be chewing up a lot of temporary space?

Any advice you could give would be helpful. There are (I think) four or six jobs scheduled at 5:00pm Pacific time every evening (which would be 0:00 GMT).

Thanks,
~Roger Whitcomb
Pivot PMC Chair


-------- Original Message --------
Subject:        Build failed in Jenkins: Pivot-trunk #622
Date:   Sat, 27 Apr 2013 00:11:37 +0000 (UTC)
From:   Apache Jenkins Server <[email protected]>
Reply-To:       [email protected]
To:     [email protected]



See<https://builds.apache.org/job/Pivot-trunk/622/>

------------------------------------------
Started by timer
Building remotely on solaris1 in 
workspace<https://builds.apache.org/job/Pivot-trunk/ws/>
Reverting<https://builds.apache.org/job/Pivot-trunk/ws/.>
Updatinghttp://svn.apache.org/repos/asf/pivot/jenkins
At revision 1476454
Reverting<https://builds.apache.org/job/Pivot-trunk/ws/pivot_trunk>
Updatinghttp://svn.apache.org/repos/asf/pivot/trunk
At revision 1476454
no change forhttp://svn.apache.org/repos/asf/pivot/jenkins  since the previous 
build
no change forhttp://svn.apache.org/repos/asf/pivot/trunk  since the previous 
build
[Pivot-trunk] $ 
/export/home/hudson/hudson-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.4/bin/ant
 check clean package test doc deploy package-tests package-sources 
package-javadoc
FATAL: command execution failed.
java.io.IOException: Cannot run program 
"/export/home/hudson/hudson-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.4/bin/ant" (in 
directory "<https://builds.apache.org/job/Pivot-trunk/ws/";)>: error=12, Not enough space
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
        at hudson.Proc$LocalProc.<init>(Proc.java:244)
        at hudson.Proc$LocalProc.<init>(Proc.java:216)
        at hudson.Launcher$LocalLauncher.launch(Launcher.java:763)
        at hudson.Launcher$ProcStarter.start(Launcher.java:353)
        at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988)
        at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955)
        at hudson.remoting.UserRequest.perform(UserRequest.java:118)
        at hudson.remoting.UserRequest.perform(UserRequest.java:48)
        at hudson.remoting.Request$2.run(Request.java:326)
        at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: error=12, Not enough space
        at java.lang.UNIXProcess.forkAndExec(Native Method)
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
        ... 15 more
Build step 'Invoke Ant' marked build as failure




Reply via email to