>> 2012/1/7 Rainer Jung <rainer.j...@kippdata.de>: >>> >>> Maybe enable the accesslog during testing with test.accesslog=true, so one >>> can check after the next failure whether the contents agree with your >>> assumption. Not sure, whether Gump offers access to the access log for >>> checking. >> >> +1, but needs some fixes in the tests that check their own access logs. >> >> IIRC they disable their own access logging and checks if that flag is >> set. That is because some time ago Tomcat allowed only single >> AccessLogValve per container. >> >> I implemented support for multiple AccessLogValves per container in >> TC7 several releases ago, so it should be possible to remove that >> logic from tests. It is somewhere on my TODO list. > > Maybe you'll get to it before I do :) >
There was only one issue with access log in the tests and I fixed it with r1228983. I updated Gump configuration for tc7 and trunk enabling the access log. We will see how it goes with next run. Those Gump projects have "<report nested="output/build/logs" />", so "access_log.yyyy-mm-dd" files there should be available, like other junit report files that are written in the same directory. I do not plan to change build.properties.default nor ask for a change in Buildbot configuration. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
