Tests log output under cruisecontrol

[ovidiu.feodorov]

There is link called "tests.log" (http://cruisecontrol.jboss.com/cc/artifacts/jms-head-testsuite/20051118050725/tests.log)
under the Build Artifacts page
(http://cruisecontrol.jboss.com/cc/artifacts/jms-head-testsuite/20051118050725)

I am wondering how is this file generated? Does cruisecontrol dump the junit process' stdout/stderr output to this file?

If this is the case, and I want to get TRACE level logging for my tests, I need to lower my CONSOLE appender threshold to TRACE, which also mean I'll get a lot of output when I run the same tests on command line. Which I would like to avoid, if at all possible.

I was wondering if it's possible to add another link on the "Build Artifacts" page to an arbitrarily specified tests.log file. I'll use this file to configure my FILE appender, so I can chose the threshold I like. The cruisecontrol process could set a propery (say "jboss.cruisecontrol.tests.result.file" or whatever) which I'll when configuring my log4j.xml FILE appender. My tests will dump logging output into that file and cruiscontrol will link that file to the "Build Artifacts" page.

[ryan.campbell]

The build artifacts page is just a dumb directory listing. For the appserver, we copy in all **/*.log under build & testsuite. We could do the same for your build, ie, just copy all the .logs. Would this work? This way, you could add logs arbitrarily to Build Artifacts without any coordination on our side.

[ovidiu.feodorov]

Yes, that's perfect.

Thanks.

[ovidiu.feodorov]

What is the current directory in which the junit process runs?

I configured my log4j to dump logging into ./messaging-tests.trace.log, which is relative to the current junit process directory, but it doesn't look like the file it's found when creating the artifacts page.

<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
 ...
 <param name="File" value="./messaging-tests.trace.log"/>
 ...

Just tell me where you want me to create that file so your artifact page generatig process finds. I don't use a "build" directory, neither a "testsuite" directory.

[ryan.campbell]

Ovidiu,

It looks like we aren't changing setting the "dir" attribute of the exec task when we call your build, so it outputs to the working directory. Rajesh will fix this.

Nevertheless, can you put the logs from your tests in output/logs? I see several things in the build script directory:

debug_output.log
messaging-tests.trace.log
jms.log
C:/dev/jboss-head/jms/tests/etc

The last one looks like it has a hard coded windows path?

All of these should go to output/logs or output/whatever.

[ovidiu.feodorov]

Setting the "dir" attribute shouldn't be necessary. I will create the log directory relative to ${module.output}. What value is this property set to during a test run?

[ryan.campbell]

It looks like using module.output will work, as it defaults like this in buildmagic.ent:

 <property name="module.root" value="${basedir}"/>
 <property name="module.output" value="${module.root}/output"/>

[ovidiu.feodorov]

Yes, but I need to know what value it defaults to during a cruiscontrol run. Is it jboss-head/jms/output or jboss-head/jms/tests/output?

If I go to the "tests" directory and I ./build.sh report, the module.output defaults to jboss-head/jms/tests/output, which is something I don't think we want to use.

What's the ${basedir} value during a cruisecontrol run?

[ryan.campbell]

The {basedir} would be jms/tests/output, just like if you exec it yourself.

What's bad about this? We'll just copy **/*.log anyway. It will catch it either way.

[ryan.campbell]

We don't override basedir, it is an ant builtin property.

[ovidiu.feodorov]

Nothing id bad. Just wanted to make sure, since I don't have access to the cc machine so I can test it myself.

[ovidiu.feodorov]

I've checked in changes that'll make the test run create its logging file under ${module.output}/logs. Looking forward to see log files linked under the Build Artifacts page.

Thanks