It has happened with other workers as well, namely 3 and 4 and then recovered. Looking at the build history it looks like a project called mango has been added to this pool of machines recently:
https://amplab.cs.berkeley.edu/jenkins/job/mango/ It looks like the slaves start to fail spark pull request builds after some runs of mango. Xin On Sat, Nov 4, 2017 at 1:23 AM, Hyukjin Kwon <gurwls...@gmail.com> wrote: > I assume it is as it says: > > Python versions prior to 2.7 are not supported. > > > Looks this happens in worker 2, 6 and 7 given my observation. > > > On 4 Nov 2017 5:15 pm, "Sean Owen" <so...@cloudera.com> wrote: > > Agree, seeing this somewhat regularly on the pull request builder. Do some > machines inadvertently have Python 2.6? some builds succeed, so may just be > one or a few. CC Shane. > > > On Thu, Nov 2, 2017 at 5:39 PM Pralabh Kumar <pralabhku...@gmail.com> > wrote: > >> Hi Dev >> >> Spark build is failing in Jenkins >> >> >> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/83353/consoleFull >> >> >> Python versions prior to 2.7 are not supported. >> Build step 'Execute shell' marked build as failure >> Archiving artifacts >> Recording test results >> ERROR: Step ?Publish JUnit test result report? failed: No test report files >> were found. Configuration error? >> >> >> Please help >> >> >> >> Regards >> >> Pralabh Kumar >> >> >
