www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: getting some StreamCorruptedException failures
Date Thu, 29 Dec 2011 19:26:26 GMT
On Thu, Dec 29, 2011 at 16:08, Niklas Gustavsson <niklas@protocol7.com> wrote:
> On Thu, Dec 29, 2011 at 1:44 PM, Andreas Veithen
> <andreas.veithen@gmail.com> wrote:
>> OK, thanks. Let me know when the upgrade is done. I will then switch a
>> couple of builds back to Ubuntu (instead of ubuntu1||ubuntu2||ubuntu3)
>> to check if that solves the issue.
>
> Done.
>
> /niklas

Now I'm getting another failure:

org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
       at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
       at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
       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:592)
       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:112)
       at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
       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:417)
       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
       at java.util.concurrent.FutureTask.run(FutureTask.java:123)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
       at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
       at hudson.maven.ExecutedMojo.getMojoClass(ExecutedMojo.java:114)
       at hudson.maven.ExecutedMojo.<init>(ExecutedMojo.java:99)
       at hudson.maven.Maven3Builder$MavenExecutionListener.recordExecutionTime(Maven3Builder.java:524)
       at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:493)
       at hudson.maven.Maven3Builder$MavenExecutionListener.forkSucceeded(Maven3Builder.java:601)
       at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:97)
       at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
       at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:383)
       at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
       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)
       ... 24 more

The first two failures actually occurred in two different builds at
the following times:

Thu Dec 29 13:31:31 UTC 2011
Thu Dec 29 13:32:01 UTC 2011

This may actually be before the upgrade. It also looks like this
affects Maven 3.0.3, but not Maven 2.2.1.

Andreas

Mime
View raw message