[jira] (CONTINUUM-2737) Projects using bazaar mayclog the prepare queue

["Brent N Atkinson (JIRA)" <ji...@codehaus.org>]

Brent N Atkinson created CONTINUUM-2737:
-------------------------------------------

             Summary: Projects using bazaar mayclog the prepare queue
                 Key: CONTINUUM-2737
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2737
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.3.8
            Reporter: Brent N Atkinson


Originally reported as part of CONTINUUM-2369, it appears that there may be an issue where projects using bazaar clog the prepare-build queue. It looks like the issue stems from an inability to complete the working copy update tasks. 

The issue appears in the continuum logs as a {{NullPointerException}} when running the {{UpdateWorkingDirectoryFromScmContinuumAction}}:
{code}
2009-09-24 13:57:43,311 [Thread-29] WARN  org.apache.continuum.scm.manager.Slf4jScmLogger  - Could not figure out of: Use --include-merges or -n0 to see merged revisions.
2009-09-24 13:57:43,410 [pool-13-thread-1] ERROR action#update-working-directory-from-scm  - Exception while executing SCM command.
org.apache.maven.scm.ScmException: Exception while executing SCM command.
	at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
	at org.apache.maven.scm.provider.bazaar.BazaarScmProvider.update(BazaarScmProvider.java:215)
	at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:851)
	at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:812)
	at org.apache.maven.scm.manager.AbstractScmManager.update(AbstractScmManager.java:555)
	at org.apache.continuum.scm.DefaultContinuumScm.update(DefaultContinuumScm.java:137)
	at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:128)
	at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.performAction(PrepareBuildProjectsTaskExecutor.java:418)
	at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.updateWorkingDirectory(PrepareBuildProjectsTaskExecutor.java:249)
	at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:148)
	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
	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:176)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
	at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
	at org.apache.maven.scm.provider.bazaar.command.changelog.BazaarChangeLogCommand.executeChangeLogCommand(BazaarChangeLogCommand.java:68)
	at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:103)
	at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:76)
	at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
	... 15 more
{code}

It may be that failure to run the action results in the project staying in the build queue.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)