Re: Test failures don't show up in e-mails

2005-11-23 Thread Emmanuel Venisse 

it isn't possible actually to obtain the test output, it will be available in 
1.1

Emmanuel

Tim McCune a écrit :

Today we got our first build failure in Continuum where a unit test
failed.  The e-mail that Continuum sent didn't actually contain the
output of the test though.  It just said:

[junit] Tests run: 6, Failures: 0, Errors: 2, Time elapsed: 0.034 sec
[junit] [ERROR] TEST com.adapt.FooTest FAILED

But didn't actually include the output of the test, so we can't find out
what failed.  Any suggestions as to what I need to change so that the
unit test output actually shows up in the e-mail?

Re: Property 'name' has no write method

2005-11-23 Thread Emmanuel Venisse 
it's a pb in our executable discover, but your maven is launch by continuum if it's in PATH. File an 
issue for it.


Emmanuel

Tim McCune a écrit :

On Mon, 2005-11-21 at 11:08 +0100, Emmanuel Venisse wrote:


do you have run it (with continuum and with maven) on the same machine?

This error isn't a pb with continuum but it's a maven error.

We write executable, arguments and working directory in logs with INFO level. Search in your logs 
ContinuumBuildExecutor:maven.



I get this output:

 WARN  ContinuumBuildExecutor:maven-1 - Could not find the executable
'maven' in this path:
WARN  ContinuumBuildExecutor:maven-1 - /usr/kerberos/bin
WARN  ContinuumBuildExecutor:maven-1 - /usr/local/bin
WARN  ContinuumBuildExecutor:maven-1 - /bin
WARN  ContinuumBuildExecutor:maven-1 - /usr/bin
WARN  ContinuumBuildExecutor:maven-1 - /usr/X11R6/bin
WARN  ContinuumBuildExecutor:maven-1 - /usr/java/jdk1.5.0/bin
WARN  ContinuumBuildExecutor:maven-1 - /usr/local/maven/bin
WARN  ContinuumBuildExecutor:maven-1 - Executable 'maven'.
INFO  ContinuumBuildExecutor:maven-1 - Arguments:  automated

As the same user, if I run which maven, I get

 /usr/local/maven/bin/maven

Doing an ls -l /usr/local/maven/bin/maven gives

-rwxr-xr-x  1 root root 4740 Dec  7  2004 /usr/local/maven/bin/maven

Maven is running though, so this seems like a bogus warning.  Any idea
what it's all about?

Re: build fails not noticed for ANT/win32

2005-11-23 Thread Antoine Brun 

Hello,

I have recently set up a continuum server in order to automate our ant 
projets integration and I am just realizing that ant build error like 
javac target compilation error are not detected as errors by continuum.
Does anyone knows anything about this? is it an Ant issue? I might be 
missing something in my ant targets definitions.


below the ant output:

compile:
   [javac] Compiling 10 source files to 
C:\dev\continuum-1.0.1\apps\continuum\working-directory\8\bin
   [javac] 
C:\dev\continuum-1.0.1\apps\continuum\working-directory\8\src\opsys\phoenix\tools\ConfManager.java:172:
 incompatible types
   [javac] found   : void
   [javac] required: opsys.solea.manager.ManagerController
   [javac]  controller = ManagerController.setProperties(props);
   [javac] ^
   [javac] 1 error

BUILD FAILED
C:\dev\continuum-1.0.1\apps\continuum\working-directory\8\build.xml:13: The 
following error occurred while executing this line:
C:\dev\continuum-1.0.1\apps\continuum\working-directory\8\build.xml:82: Compile 
failed; see the compiler error output for details.

the javac target:

   target name=compile depends=init
   javac debug=yes srcdir=${basedir}/src destdir=${basedir}/bin fork=true source=1.5 
nowarn=on failonerror=true
   classpath refid=compile.appli.classpath /
   /javac
   copy todir=${basedir}/bin
fileset dir=${basedir}/src includes=**/*Help.html **/*.gif **/*.png 
excludes=**/*.java CVS CVS/* **/CVS **/CVS/* /
   /copy
   /target


Thank you,


Antoine Brun