geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Jiang <genspr...@gmail.com>
Subject Re: Trunk Builds
Date Thu, 02 Jul 2009 02:41:11 GMT
If the test is wrong, tomcat run-as propagation logic must have bug because
Tomcat testsuite with the same case passed.
On Thu, Jul 2, 2009 at 9:53 AM, David Jencks <david_jencks@yahoo.com> wrote:

>
> On Jul 1, 2009, at 6:31 PM, Shawn Jiang 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.
>
>
> The run-as propagation from servlet to servlet is not really specified in
> the servlet spec and I may have changed it in jetty7 after talking with Ron
> Monzilla the sun security spec guy.  IIRC jetty7 interprests run-as to apply
> to the target servlet in a dsipatch whether or not the servlets are in the
> same web app.  IIRC the previous behavior was that run-as was only applied
> in a cross-context dispatch.  So most likely the test is wrong.
>
> thanks
> david jencks
>
>
> On Thu, Jun 25, 2009 at 11:58 PM, Jarek Gawor <jgawor@gmail.com> 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<kevan.miller@gmail.com>
>> 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

Mime
View raw message