2011/2/17 Rainer Jung <[email protected]>: > I get test suite failures for TC 7 right now. I'm not sure whether it is > because I changed my testing environment, but the failure seems to be pretty > special, namely a NullPointerException in MBeanUtils.createObjectName() line > 532. >
I have an old working copy (updated yesterday), i.e. before Mark's http://svn.apache.org/viewvc?view=revision&revision=1071556 and I also observe those NPEs with namingResources.mbeanDestroyFail So it is not specific to your environment. I do not know yet whether any of today's commits fixes them. (BTW, seeing plain "namingResources.mbeanDestroyFail" in the logs means that the message is not found in the resource file.) -------------------- These failures (and no nagging about them on the list) mean that there is no CI tool that runs the tests for us. The buildbot runs "ant release" and the "release" target does not depend on the "test" one. http://ci.apache.org/builders/tomcat-trunk/ Shouldn't we ask buildbot admins to replace that with "ant release test"? I do not quite remember how it was configured previously (I think that "ant test" was a separate step in the build sequence, named like "compile_1"). Apparently Gump does not test it either. Any more ideas how CI testing should be configured? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
