Hey Seb, I’ll also take a look. @Lewis could potentially help here too. Lewis any time to scope?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Director, Information Retrieval and Data Science Group (IRDS) Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA WWW: http://irds.usc.edu/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 4/18/16, 4:40 AM, "Sebastian Nagel" <wastl.na...@googlemail.com> wrote: >Hi, > >the last successful builds for both branches > https://builds.apache.org/job/Nutch-trunk/ > https://builds.apache.org/job/Nutch-nutchgora/ >were in February before the svn to git migration. > >The reason is probably a changed path to the build workspace. >When comparing the logs > https://builds.apache.org/job/Nutch-trunk/3356/consoleText >and > https://builds.apache.org/job/Nutch-trunk/3360/consoleText > >(3356, svn) > Buildfile: /home/jenkins/jenkins-slave/workspace/Nutch-trunk/trunk/build.xml > >(3360, git) > Buildfile: /home/jenkins/jenkins-slave/workspace/Nutch-trunk/build.xml > >Although the ant build succeeds, the XML test reports are not found which >causes >the build to be marked as failed: > >(3360, git) >BUILD SUCCESSFUL >Total time: 12 minutes 37 seconds >[xUnit] [INFO] - Starting to record. >[xUnit] [INFO] - Processing JUnit >[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern >'trunk/build/test/TEST-*.xml' relative to >'/home/jenkins/jenkins-slave/workspace/Nutch-trunk' for >the testing framework 'JUnit'. Did you enter a pattern relative to the >correct directory? Did you >generate the result report(s) for 'JUnit'? >... >Finished: FAILURE > > >Does anyone know how to fix this? >I could dig into it later today or tomorrow. > >Thanks, >Sebastian
