Builders:
I've noticed that maven builds (like Flume's) seem to consistently fail on
ubuntu2 due to failures to read the jar files in the local m2 repo. I see
this whenever Flume happens to hit ubuntu2:
[INFO] *--- maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) @ flume-ng-core ---*[INFO]
-------------------------------------------------------------[ERROR]
COMPILATION ERROR : [INFO]
-------------------------------------------------------------[ERROR]
error: error reading
/home/hudson/.m2/repository/javax/jms/jms/1.1/jms-1.1.jar; error in
opening zip file[INFO] 1 error
[INFO] -------------------------------------------------------------
and later
message : Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) on project flume-ng-core: Compilation failure
error: error reading
/home/hudson/.m2/repository/javax/jms/jms/1.1/jms-1.1.jar; error in
opening zip file
cause : Compilation failure
error: error reading
/home/hudson/.m2/repository/javax/jms/jms/1.1/jms-1.1.jar; error in
opening zip file
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) on project flume-ng-core: Compilation failure
error: error reading
/home/hudson/.m2/repository/javax/jms/jms/1.1/jms-1.1.jar; error in
opening zip file
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at
org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:122)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:74)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException:
Compilation failure
Here's the list of recent Flume build failures. Note the clustering on
ubuntu2. Manually triggering the builds cause them to succeed on other
ubuntu slaves. Not a critical issue, but it probably affects other
projects. Probably just a permission or /home mount issue.
Let me know if I can help debug / fix. Thanks!
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
