Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-19292

Mahout builds failing in jenkins

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: None
    • Component/s: Jenkins
    • Labels:
      None
    • Project:
      Mahout

      Description

      when kiking off a manual build of mahout, i am getting this:

      Started by user apalumbo
      Running as SYSTEM
      [EnvInject] - Loading node environment variables.
      Building remotely on H31 (ubuntu) in workspace /home/jenkins/jenkins-slave/workspace/mahout-nightly
      ERROR: A Maven installation needs to be available for this project to be built.Either your server has no Maven installations defined, or the requested Maven version does not exist.
      Retrying after 10 seconds
      ERROR: A Maven installation needs to be available for this project to be built.Either your server has no Maven installations defined, or the requested Maven version does not exist.
      Retrying after 10 seconds
      ERROR: A Maven installation needs to be available for this project to be built.Either your server has no Maven installations defined, or the requested Maven version does not exist.
      Sending e-mails to: dev@mahout.apache.org
      Finished: FAILURE

      we require maven 3.3.3, would this be the issue? I don't believe so, because these failures are going back to May, when we disabled Jenkins Nightly builds, and mahout-quality. At that time, I don't believe that we had a requirement for maven 3.3.3

      We can see that the build (nightly) was fine on [master] until I just kicked off a manual build. (it says via SCM change, but was logged into jenkins and clicked start build now.)



      The log from the first failure: (actually here we can se that there is no access to mvn.) Thanks

      --Andy Palumbo

      See <https://builds.apache.org/job/Mahout-Quality/3599/display/redirect&gt;Changes:------------------------------------------Started by an SCM changeStarted by user apalumboRebuilds build #3598Running as SYSTEM[EnvInject] - Loading node environment variables.Building remotely on H40 (ubuntu xenial) in workspace <https://builds.apache.org/job/Mahout-Quality/ws/&gt;No credentials specifiedCloning the remote Git repositoryCloning repository https://git-wip-us.apache.org/repos/asf/mahout.git > git init <https://builds.apache.org/job/Mahout-Quality/ws/> # timeout=10Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/mahout.git > git --version # timeout=10 > git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/mahout.git +refs/heads/:refs/remotes/origin/ > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/mahout.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/mahout.git # timeout=10Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/mahout.git > git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/mahout.git +refs/heads/:refs/remotes/origin/ > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 2a374a6b41e241627d3c2e247da7ee251df62805 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2a374a6b41e241627d3c2e247da7ee251df62805Commit message: "[MAHOUT-2069] fix typo in core/pom.xml" > git rev-list --no-walk 2a374a6b41e241627d3c2e247da7ee251df62805 # timeout=10[Mahout-Quality] $ mvn -f pom.xml -U clean install findbugs:findbugs pmd:pmd -Dmaven.javadoc.skip=trueFATAL: command execution failedjava.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H40 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.tasks.Maven.perform(Maven.java:368) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused: java.io.IOException: Cannot run program "mvn" (in directory "<https://builds.apache.org/job/Mahout-Quality/ws/")>: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.<init>(Proc.java:250) at hudson.Proc$LocalProc.<init>(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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:748)Build step 'Invoke top-level Maven targets' marked build as failureArchiving artifactsRecording test resultsERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?Publishing Javadoc

        Attachments

        1. Screen Shot 2019-10-17 at 3.44.39 AM.png
          63 kB
          Andrew Palumbo
        2. Screen Shot 2019-10-17 at 3.44.08 AM.png
          367 kB
          Andrew Palumbo

          Activity

            People

            • Assignee:
              gmcdonald Gavin McDonald
              Reporter:
              Andrew_Palumbo Andrew Palumbo
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: