2012/3/7 Mark Thomas <ma...@apache.org>: > On 06/03/2012 21:27, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2816 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1297717 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 > > Drat. The Comet unit tests are still failing. I had hoped we had fixed that. > > We really need the Gump run to fail so we have access to the full logs > to better understand which test is failing and why. Either that or a way > to extract the logs from buildbot. Hmm. I probably have access to that > machine. I'll go and have a look. >
It is possible to make junit to spew the logs onto stdout by defining junit.formatter.usefile=false I mentioned that in https://issues.apache.org/jira/browse/INFRA-3948 Maybe go this way, because the task of providing us access to separate log files like in Gump has no progress at all. >From RAT report I know that buildbot has build.properties file in the root of the project. I do not know how it is created - probably by some shell script. The new property can be added there. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
