Sorry for delay. Not much time. Please see patch below. I change build.log location as now it doesn't work when target "test" is called because the same file is used with another recorder within the build simultaneously (see init target). So either I've had to change how "maybejars" target gets called in which case the recorder log level would have been changed from what it was by default to error, or introduce a log file for the test target only. I preferred the second approach as it logs at info level. So allows for more assurance that we're processing the right log. As well it will allow later to implement a check to compare tests executed with test results produced (remember tests overwriting). Should I disable the build.log generation? I don't believe it ever worked when test target is called (it does for any other targets though)? Or should I move it to output dir as well? Or should I leave it as is? Index: testsuite/build.xml =================================================================== --- testsuite/build.xml (revision 68976) +++ testsuite/build.xml (working copy) @@ -873,7 +873,7 @@ --> - + @@ -897,7 +897,20 @@ - + + + + + + + + + + + + + <fail message="Some servers failed to shutdown cleanly." + if="servers.shutdown.failed"/> <target name="tests-stress" description="Execute all stress tests." View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122223#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...