continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (CONTINUUM-2203) Parallel builds sporadically failing
Date Sun, 26 Apr 2009 23:44:44 GMT

     [ http://jira.codehaus.org/browse/CONTINUUM-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated CONTINUUM-2203:
------------------------------------

    Fix Version/s: 1.3.3

> Parallel builds sporadically failing
> ------------------------------------
>
>                 Key: CONTINUUM-2203
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2203
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.3.3
>         Environment: Maven version: 2.0.10
> Java version: 1.4.2_19
> OS name: "linux" version: "2.6.27.21" arch: "i386" Family: "unix"
> glassfish-v2.1-b60e-linux-ml
>            Reporter: Christian Schulte
>             Fix For: 1.3.3
>
>         Attachments: Build Definitions.png
>
>
> There seem to be problems with parallel builds. Sometimes builds fail and continuum then
seems to have lost track of them - that is - there is no state icon shown in the projectgroup
overview page for these builds. Currently I can only provide some stacktraces from the logs
and from the build output.
> {code}
> org.apache.maven.continuum.notification.NotificationException: INTERNAL ERROR: The current
build wasn't the first in the build list. Current build: '305', first build: '306
> '.
>         at org.apache.maven.continuum.notification.AbstractContinuumNotifier.getPreviousBuild(AbstractContinuumNotifier.java:294)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:296)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:284)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:196)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:97)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:240)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:192)
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
>         at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>         at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>         at java.lang.Thread.run(Thread.java:619)
> {code}
> {code}
> org.apache.maven.continuum.notification.NotificationException: INTERNAL ERROR: The current
build wasn't the first in the build list. Current build: '315', first build: '316'.
>         at org.apache.maven.continuum.notification.AbstractContinuumNotifier.getPreviousBuild(AbstractContinuumNotifier.java:294)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:296)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:284)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:196)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:97)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:240)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:192)
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
>         at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>         at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>         at java.lang.Thread.run(Thread.java:619)
> {code}
> {code}
> org.apache.maven.continuum.notification.NotificationException: INTERNAL ERROR: The current
build wasn't the first in the build list. Current build: '325', first build: '326'.
>         at org.apache.maven.continuum.notification.AbstractContinuumNotifier.getPreviousBuild(AbstractContinuumNotifier.java:294)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:296)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:284)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:196)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:97)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:240)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:192)
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
>         at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>         at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>         at java.lang.Thread.run(Thread.java:619)
> {code}
> {code}
> org.apache.maven.continuum.notification.NotificationException: INTERNAL ERROR: The current
build wasn't the first in the build list. Current build: '344', first build: '346'.
>         at org.apache.maven.continuum.notification.AbstractContinuumNotifier.getPreviousBuild(AbstractContinuumNotifier.java:294)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:296)
>         at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:284)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:196)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:151)
>         at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:97)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:240)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:192)
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
>         at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>         at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>         at java.lang.Thread.run(Thread.java:619)
> {code}
> The following exceptions seem to be the reason why continuum refuses to schedule such
failed builds automatically. I need to build those projects manually once they failed to make
things work again.
> {code}
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Can't determine if the
project should build or not
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.shouldBuild(DefaultBuildController.java:534)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:143)
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
>         at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>         at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.NullPointerException
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.shouldBuild(DefaultBuildController.java:527)
>         ... 8 more
> {code}
> {code}
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Can't determine if the
project should build or not
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.shouldBuild(DefaultBuildController.java:534)
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:143)
>         at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
>         at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>         at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
>         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: java.lang.NullPointerException
>         at org.apache.maven.continuum.buildcontroller.DefaultBuildController.shouldBuild(DefaultBuildController.java:527)
>         ... 8 more
> {code}
> This happened once when running 'clean site-deploy'. Scary.
> {code}
> [INFO] Generating &quot;Dependencies&quot; report.
> #
> # An unexpected error has been detected by HotSpot Virtual Machine:
> #
> #  SIGBUS (0x7) at pc=0xb79adfb0, pid=6143, tid=3085551280
> #
> # Java VM: Java HotSpot(TM) Client VM (1.4.2_19-b04 mixed mode)
> # Problematic frame:
> # C  [libzip.so+0xafb0]
> #
> # An error report file with more information is saved as hs_err_pid6143.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> {code}
> This shows a failing javadoc report in the build output due to a missing directory. The
only reason I think this could happen is when another build was running in parallel and did
a 'clean' while that javadoc report was still running. For all project groups I setup two
build definitions 'clean deploy' and 'clean site-deploy' at group level. 'clean deploy' with
a hourly schedule, 'clean site-deploy' with a weekly schedule. Just today the weekly schedule
seems to have triggered and was run in parallel with the 'clean deploy' definition. Just guessing,
though.
> {code}
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - javadoc: error - Unable
to create directory /var/spool/continuum/working-directory/134/target/site/apidocs/some/package/
> com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
> 	at com.sun.tools.doclets.internal.toolkit.util.DirectoryManager.createDirectory(DirectoryManager.java:263)
> 	at com.sun.tools.doclets.internal.toolkit.util.Util.genWriter(Util.java:576)
> 	at com.sun.tools.doclets.formats.html.markup.HtmlWriter.&lt;init&gt;(HtmlWriter.java:61)
> 	at com.sun.tools.doclets.formats.html.markup.HtmlDocWriter.&lt;init&gt;(HtmlDocWriter.java:47)
> 	at com.sun.tools.doclets.formats.html.HtmlDocletWriter.&lt;init&gt;(HtmlDocletWriter.java:95)
> 	at com.sun.tools.doclets.formats.html.SubWriterHolderWriter.&lt;init&gt;(SubWriterHolderWriter.java:40)
> 	at com.sun.tools.doclets.formats.html.ClassWriterImpl.&lt;init&gt;(ClassWriterImpl.java:49)
> 	at com.sun.tools.doclets.formats.html.WriterFactoryImpl.getClassWriter(WriterFactoryImpl.java:64)
> 	at com.sun.tools.doclets.internal.toolkit.builders.BuilderFactory.getClassBuilder(BuilderFactory.java:83)
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:152)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:164)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:106)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> 	at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> 	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 com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> 	at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> 	at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> 	at com.sun.tools.javadoc.Start.begin(Start.java:128)
> 	at com.sun.tools.javadoc.Main.execute(Main.java:41)
> 	at com.sun.tools.javadoc.Main.main(Main.java:31)
> com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:159)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:164)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:106)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> 	at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> 	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 com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> 	at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> 	at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> 	at com.sun.tools.javadoc.Start.begin(Start.java:128)
> 	at com.sun.tools.javadoc.Main.execute(Main.java:41)
> 	at com.sun.tools.javadoc.Main.main(Main.java:31)
> Command line was:/usr/lib/jvm/java-6-sun-1.6.0.12/bin/javadoc @options @packages
> {code}
> Same with this.
> {code}
> [INFO] Error uploading site
> Embedded error: Error performing commands for file transfer
> Exit code: 0 - error:  cannot delete old xref-test/overview-frame.html
> error:  cannot delete old xref-test/some/package/package-frame.html
> error:  cannot delete old xref/overview-frame.html
> error:  cannot delete old apidocs/allclasses-noframe.html
> error:  cannot delete old apidocs/src-html/some/package/SomeFile.html
> error:  cannot delete old apidocs/resources/inherit.gif
> {code}
> {code}
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - javadoc: error - Unable
to create directory /var/spool/continuum/working-directory/139/target/site/apidocs/some/package/
> com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
> 	at com.sun.tools.doclets.internal.toolkit.util.DirectoryManager.createDirectory(DirectoryManager.java:263)
> 	at com.sun.tools.doclets.internal.toolkit.util.Util.genWriter(Util.java:576)
> 	at com.sun.tools.doclets.formats.html.markup.HtmlWriter.&lt;init&gt;(HtmlWriter.java:61)
> 	at com.sun.tools.doclets.formats.html.markup.HtmlDocWriter.&lt;init&gt;(HtmlDocWriter.java:47)
> 	at com.sun.tools.doclets.formats.html.HtmlDocletWriter.&lt;init&gt;(HtmlDocletWriter.java:95)
> 	at com.sun.tools.doclets.formats.html.SubWriterHolderWriter.&lt;init&gt;(SubWriterHolderWriter.java:40)
> 	at com.sun.tools.doclets.formats.html.ClassWriterImpl.&lt;init&gt;(ClassWriterImpl.java:49)
> 	at com.sun.tools.doclets.formats.html.WriterFactoryImpl.getClassWriter(WriterFactoryImpl.java:64)
> 	at com.sun.tools.doclets.internal.toolkit.builders.BuilderFactory.getClassBuilder(BuilderFactory.java:83)
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:152)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:164)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:106)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> 	at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> 	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 com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> 	at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> 	at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> 	at com.sun.tools.javadoc.Start.begin(Start.java:128)
> 	at com.sun.tools.javadoc.Main.execute(Main.java:41)
> 	at com.sun.tools.javadoc.Main.main(Main.java:31)
> com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(HtmlDoclet.java:159)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles(AbstractDoclet.java:164)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:106)
> 	at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> 	at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> 	at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> 	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 com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> 	at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> 	at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> 	at com.sun.tools.javadoc.Start.begin(Start.java:128)
> 	at com.sun.tools.javadoc.Main.execute(Main.java:41)
> 	at com.sun.tools.javadoc.Main.main(Main.java:31)
> Command line was:/usr/lib/jvm/java-6-sun-1.6.0.12/bin/javadoc @options @packages
> {code}
> Then there is this failing build. What is special with this build is that it downloaded
various dependencies which it shouldn't have done. Maybe the local repository got purged automatically
in between ? It's downloading releases and I think purging does not touch release artifacts
?
> {code}
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] org/apache/maven/model/PluginManagement
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NoClassDefFoundError: org/apache/maven/model/PluginManagement
> 	at org.apache.maven.report.projectinfo.PluginManagementReport.canGenerateReport(PluginManagementReport.java:106)
> 	at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports(AbstractSiteRenderingMojo.java:177)
> 	at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:81)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
> 	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:324)
> 	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> 	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> 	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> 	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {code}
> No idea about this one. Seems some archive file was invalid. So it could be some build
was running in parallel and was updating some jar file when this failing build was trying
to use it.
> {code}
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] invalid block type
> [INFO] ------------------------------------------------------------------------
> {code}
> This one was shown as the build output for one of those failing builds.
> {code}
> java.lang.NullPointerException
> 	at org.apache.maven.continuum.buildcontroller.DefaultBuildController.shouldBuild(DefaultBuildController.java:527)
> 	at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:143)
> 	at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:48)
> 	at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
> 	at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
> 	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
> 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> 	at java.lang.Thread.run(Thread.java:619)
> {code}
> I have setup two project groups with theire own local repositories. So it normally cannot
happen that parallel builds are accessing the same local repository. The failing builds are
all in the same group. It really seems that things are running in parallel which shouldn't.
Let me know if you need any more information. As said, I cannot reproduce it but it happens
regularly with builds which have been scheduled automatically.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message