Based on running the testsuite yesterday and with fixes committed last night I *think* we should be passing all tests on Tomcat and fail enterprise-testsuite/sec-tests and webservices-testsuite/jaxws-tests on Jetty. The webservices-testsuite/jaxws-tests fails because of GERONIMO-4645. Not sure what's going on with enterprise-testsuite/sec-tests.
Jarek On Thu, Jun 25, 2009 at 11:00 AM, Kevan Miller<[email protected]> wrote: > A search of emails shows that our last successful automated build of trunk > was on May 26th. I know that there have been increasing frustration with > these recent build issues. We seem to be closing in on getting these issues > resolved. I built last night. I built successfully, last night, but had 7 > testsuite failures -- 3 jetty, 4 tomcat. > > I think it would do us a lot of good to have a concerted effort to get these > final issues resolved. Here are the test failures that I'm seeing: > > 3 common errors: > > [INFO] The following tests failed: > [INFO] * console-testsuite/advanced - > /Users/kevan/geronimo/server/trunk/testsuite/console-testsuite/advanced/build.log > [INFO] * enterprise-testsuite/sec-tests - > /Users/kevan/geronimo/server/trunk/testsuite/enterprise-testsuite/sec-tests/build.log > [INFO] * webservices-testsuite/jaxws-tests - > /Users/kevan/geronimo/server/trunk/testsuite/webservices-testsuite/jaxws-tests/build.log > > 1 Tomcat unique failure: > > [INFO] * web-testsuite/test-tomcat - > /Users/kevan/geronimo/server/trunk/testsuite/web-testsuite/test-tomcat/build.log > > Is this consistent with what others are seeing? > > --kevan >
