unable to have results when build is cancelled

2007-08-30 Thread remi . chevalier
Hi,
I work on Continuum-1.1-beta-2 (thanks for this tool) and when I just 
noticed that when a build is cancelled, I only obtain this result:

org.apache.maven.continuum.execution.ContinuumBuildCancelledException: The 
build was cancelled
 at 
org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:215)
 at 
org.apache.maven.continuum.execution.ant.AntBuildExecutor.build(AntBuildExecutor.java:106)
 at 
org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:140)
 at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:406)
 at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:145)
 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:595)
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:203)
 ... 11 more
Caused by: java.lang.InterruptedException
 at java.lang.ProcessImpl.waitFor(Native Method)
 at 
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:128)
 ... 15 more

Is it the normal works? Because if the build was cancelled by a timeout 
that I defined, I would like to see which test is looping.
When I run manualy the build I can see what happens in the build results 
as one goes along, but just after I cancelled the build, these results are 
subsituted by the error above.
Can someone tell me if it's normal and if not, what's the problem?

Thank you,
Rémi.
+-+
Combining consulting and technology solutions offers enables Devoteam
to provide its customers with independent advice and effective solutions
that meet their strategic objectives (IT performance and optimisation)
in complementary areas: networks, systems infrastructure, security
and e-business applications.
Created in 1995, Devoteam achieved in 2005 a turnover of 199 million euros
and an operating margin of 7%. The group counts 2,400 employees through
sixteen countries in Europe, the Middle East and North Africa.
Listed on Euronext (Eurolist B compartment) since October 28, 1999.
Part of the Nexteconomy, CAC SMALL 90, IT CAC 50, SBF 250 index of
Euronext Paris
ISIN: FR 07379 3, Reuters: DVTM.LM, Bloomberg: DEVO FP
+-+


Re: unable to have results when build is cancelled

2007-08-30 Thread Emmanuel Venisse

Please file an issue, a build result must be saved with the process output it 
it is available.

Emmanuel

[EMAIL PROTECTED] a écrit :

Hi,
I work on Continuum-1.1-beta-2 (thanks for this tool) and when I just 
noticed that when a build is cancelled, I only obtain this result:


org.apache.maven.continuum.execution.ContinuumBuildCancelledException: The 
build was cancelled
 at 
org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:215)
 at 
org.apache.maven.continuum.execution.ant.AntBuildExecutor.build(AntBuildExecutor.java:106)
 at 
org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:140)
 at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:406)
 at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:145)
 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:595)
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:203)

 ... 11 more
Caused by: java.lang.InterruptedException
 at java.lang.ProcessImpl.waitFor(Native Method)
 at 
org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:128)

 ... 15 more

Is it the normal works? Because if the build was cancelled by a timeout 
that I defined, I would like to see which test is looping.
When I run manualy the build I can see what happens in the build results 
as one goes along, but just after I cancelled the build, these results are 
subsituted by the error above.

Can someone tell me if it's normal and if not, what's the problem?

Thank you,
Rémi.
+-+
Combining consulting and technology solutions offers enables Devoteam
to provide its customers with independent advice and effective solutions
that meet their strategic objectives (IT performance and optimisation)
in complementary areas: networks, systems infrastructure, security
and e-business applications.
Created in 1995, Devoteam achieved in 2005 a turnover of 199 million euros
and an operating margin of 7%. The group counts 2,400 employees through
sixteen countries in Europe, the Middle East and North Africa.
Listed on Euronext (Eurolist B compartment) since October 28, 1999.
Part of the Nexteconomy, CAC SMALL 90, IT CAC 50, SBF 250 index of 
Euronext Paris

ISIN: FR 07379 3, Reuters: DVTM.LM, Bloomberg: DEVO FP
+-+