A quick solution is to disable the offending host in your Jenkins configuration.
Thanks, Roman. On Tue, Sep 19, 2017 at 12:15 PM, Jingyi Mei <[email protected]> wrote: > Hi Ed, > > Thanks for referring to the INFRA issue. Seems there is no quick solution > for that yet. And since I kept getting the same error for my PR, I am going > to create another issue specifically for unblocking my build. > > Thank you very much! > Jingyi > > On Mon, Sep 18, 2017 at 8:23 PM, Ed Espino <[email protected]> wrote: > >> Hey Jingyi, >> >> Welcome to the project. These types of issues do happen from time to time. >> There is a recent Infrastructure issue which references the same system >> that your MADlib PR build hit. >> >> Jira: INFRA-14979 >> Summary: Jenkins jobs on qnode3 are failing with "No space left on device" >> Jira link: https://issues.apache.org/jira/browse/INFRA-14979 >> >> If the problem persists, please file an Infrastructure (INFRA) ticket so it >> can be addressed. There is a good chance it impacts other projects as well. >> >> Thanks, >> -=e >> >> >> On Mon, Sep 18, 2017 at 2:25 PM, Jingyi Mei <[email protected]> wrote: >> >> > Hi developers, >> > >> > Recently, I kept getting build failure on Jenkins for infra reasons, >> error >> > message is as following: >> > >> > ------------------------------------------------------- >> > >> > FATAL: Unable to produce a script file >> > java.io.IOException: No space left on device >> > at java.io.FileOutputStream.writeBytes(Native Method) >> > at java.io.FileOutputStream.write(FileOutputStream.java:326) >> > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) >> > at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:316) >> > at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:149) >> > at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233) >> > at hudson.FilePath$17.invoke(FilePath.java:1380) >> > at hudson.FilePath$17.invoke(FilePath.java:1363) >> > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2739) >> > at hudson.remoting.UserRequest.perform(UserRequest.java:153) >> > at hudson.remoting.UserRequest.perform(UserRequest.java:50) >> > at hudson.remoting.Request$2.run(Request.java:336) >> > at hudson.remoting.InterceptingExecutorService$1.call( >> > InterceptingExecutorService.java:68) >> > at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> > at java.util.concurrent.ThreadPoolExecutor.runWorker( >> > ThreadPoolExecutor.java:1142) >> > at java.util.concurrent.ThreadPoolExecutor$Worker.run( >> > ThreadPoolExecutor.java:617) >> > at java.lang.Thread.run(Thread.java:745) >> > at ......remote call to qnode3(Native Method) >> > at hudson.remoting.Channel.attachCallSiteStackTrace( >> > Channel.java:1545) >> > at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) >> > at hudson.remoting.Channel.call(Channel.java:830) >> > at hudson.FilePath.act(FilePath.java:986) >> > Caused: java.io.IOException: remote file operation failed: >> > /home/jenkins/jenkins-slave/workspace/madlib-pr-build >> > >> > ------------------------------------------------------------ >> > >> > >> > It seems that for a specific PR, it was always sent to a specific test >> > machine and that machine always didn't have enough space. >> > >> > >> > Does any one know how to fix this? >> > >> > >> > Thanks, >> > >> > Jingyi >> > >> >> >> >> -- >> *Ed Espino* >>
