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-1634) Normal build output should not be replaced by timeout stacktrace when build is timed out
Date Wed, 02 Apr 2008 05:01:02 GMT

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

Brett Porter updated CONTINUUM-1634:
------------------------------------

    Fix Version/s: 1.x

> Normal build output should not be replaced by timeout stacktrace when build is timed
out
> ----------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1634
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1634
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Damien Lecan
>             Fix For: 1.x
>
>
> When a build timeout is thrown, normal build output is replaced by an ugly and unuseful
stacktrace (see below).
> Is it possible to keep the normal build output ? Is it available somewhere ?
> Thanks
> Stacktrace :
> {code} 
> org.apache.maven.continuum.execution.ContinuumBuildCancelledException:
> The build was cancelled
>       at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:214)
>       at org.apache.maven.continuum.execution.maven.m1.MavenOneBuildExecutor.build(MavenOneBuildExecutor.java:106)
>       at org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:118)
>       at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:408)
>       at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:147)
>       at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
>       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$Worker.runTask(ThreadPoolExecutor.java:665)
>       at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>       at java.lang.Thread.run(Thread.java:619)
> Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error
> while executing external command, process killed.
>       at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:164)
>       at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:89)
>       at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand(DefaultShellCommandHelper.java:114)
>       at org.apache.maven.continuum.utils.shell.DefaultShellCommandHelper.executeShellCommand(DefaultShellCommandHelper.java:59)
>       at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:202)
>       ... 11 more
> Caused by: java.lang.InterruptedException
>       at java.lang.Object.wait(Native Method)
>       at java.lang.Object.wait(Object.java:485)
>       at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165)
>       at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:128)
> {code}

-- 
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