NJ, I took a quick look at the build console output and it appears "qnode3 (ubuntu)" has exhausted it's available disk space. Additionally, it looks as if this system has been indulging a bit too much lately (too many Stan's donuts?) impacting other Jenkins jobs: https://issues.apache.org/jira/browse/INFRA-14838?jql=text%20~%20%22qnode3%22
I also triggered additional PR builds and they all failed as they went to the same Jenkins build resource. I have added a comment to INFRA-14838 for the MADlib PR build issue. You may need to open a new INFRA ticket to address this current issues. Top of build console output identifying the Jenkins build slave resource: Building remotely on qnode3 <https://builds.apache.org/computer/qnode3> (ubuntu) in workspace /home/jenkins/jenkins-slave/workspace/madlib-pr-build -=e On Fri, Aug 18, 2017 at 10:53 AM, Nandish Jayaram <njaya...@pivotal.io> wrote: > Hi, > > The latest PR build on Jenkins ( > https://builds.apache.org/user/riyer/my-views/view/ > MADlib-Monitor/job/madlib-pr-build/170/) > is failing with an > `java.io.IOException: No space left on device` error. > Can somebody with a Jenkins account have a look at > it please? > > NJ > -- *Ed Espino*
