On Fri, Jul 3, 2009 at 2:53 AM, Jarek Gawor <[email protected]> wrote:
> Shawn, > > The one failure in console/advanced on Tomcat is caused by fixing that > prompting issue in the console. I'm hoping it's just a timing issue It's not a timing issue. This is caused by a modification on ConfirmMessageTag.java recently . After that change, dojo.js can't be found so that the prompting dialog can't be display anymore. Revert the bvt change and update the code private static final String DOJO_BASE = "/dojo/dojo" to private static final String DOJO_BASE = "/dojo" can fix this. > > since its takes a bit of time to load all the Dojo stuff for the first > time. So I just increased the wait time for the window to show up in > that test. > > Jarek > > On Wed, Jul 1, 2009 at 9:31 PM, Shawn Jiang<[email protected]> wrote: > > I can't recreate the same console/advanced failure in my local machine. > > But I do find another console testsuite bug and filed a JIRA: > > https://issues.apache.org/jira/browse/GERONIMO-4720 (patch provided) > > The failure of enterprise-testsuite/sec-tests is related to > > "run-as" propagation from a servlet to another servlet. I'm looking > into > > it and will provide a patch. > > On Thu, Jun 25, 2009 at 11:58 PM, Jarek Gawor <[email protected]> wrote: > >> > >> 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 > >> > > > > > > > > > -- > > Shawn > > > -- Shawn
