Team, 1. It seems the simulator-gate project in that view, was not able to fetch the code using jenkins git plugin and is stuck as per below message. This job is failing continuously with no use as of now.
2. If possible, can i get the access to simulator node? Currently, i don't have access to it. I can check to see if i can fix this job, using few articles available out there, if i can get access. Hugo, I believe you fixed a similar issue on other nodes for failing git fetch timeouts? thoughts? Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on simulator in workspace /var/lib/jenkins/simulator-gate Fetching changes from the remote Git repository Fetching upstream changes from https://github.com/apache/cloudstack ERROR: Timeout after 10 minutes FATAL: Failed to fetch from https://github.com/apache/cloudstack hudson.plugins.git.GitException: Failed to fetch from https://github.com/apache/cloudstack at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/apache/cloudstack +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Reusing existing pack: 471153, done. remote: Counting objects: 442, done. remote: Compressing objects: 0% (1/379) remote: Compressing objects: 1% (4/379) remote: Compressing objects: 2% (8/379) remote: Compressing objects: 3% (12/379) remote: Compressing objects: 4% (16/379) Regards, Santhosh ________________________________________ From: Prasanna Santhanam [t...@apache.org] Sent: Friday, January 24, 2014 11:24 AM To: dev@cloudstack.apache.org Subject: Re: Jenkins bacd: Simulator-build Job Failing On Fri, Jan 24, 2014 at 02:50:54PM +0000, Santhosh Edukulla wrote: > Team, > > Simulator-build Job failing with log @ > http://jenkins.buildacloud.org/view/simulator/job/simulator-build/lastBuild/console > as below. Please let us know if we can do something to bring this job up. > > CATALINA_HOME=/usr/share/apache-tomcat-6.0.33 > ++ export M2_HOME=/usr/share/apache-maven-3.0.5 > ++ M2_HOME=/usr/share/apache-maven-3.0.5 > ++ export > PATH=/usr/share/apache-maven-3.0.5/bin:/usr/share/apache-maven-3.0.5/bin:/usr/local/bin:/bin:/usr/bin > ++ > PATH=/usr/share/apache-maven-3.0.5/bin:/usr/share/apache-maven-3.0.5/bin:/usr/local/bin:/bin:/usr/bin > ++ export 'MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=500m' > ++ MAVEN_OPTS='-Xmx1024m -XX:MaxPermSize=500m' > + mvn -Pdeveloper -Dsimulator -DskipTests clean install > Error occurred during initialization of VM > Cannot create VM thread. Out of system resources. > Build step 'Execute shell' marked build as failure > Finished: FAILURE All the failing jobs may have launched too many JVMs and eaten up resources. Would need to login to the simulator slave on jenkins and kill the hung jobs. Ideally, stop-jetty job will stop the started java instance of the management server, but I think someone may have removed that target which Ian had put in a while ago. > > > Thanks! > Santhosh -- Prasanna., ------------------------ Powered by BigRock.com
