You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jason Dillon <ja...@planet57.com> on 2008/05/07 12:42:07 UTC
Re: [BUILD] trunk: Successful
FYI, I changed the top-level testsuite module to use the shitty-maven-
plugin to invoke the children *-testsuite modules, which forks off
another mvn process for each and seems to hang less due to weird ant/
maven/groovy/whatever gremlins.
I'm also doing a test now of using just one geronimo:start-server (and
selenium bits) at the very top-level to see if that improves the time
to run the testsuite... and doesn't cause weird problems.
--jason
On May 7, 2008, at 3:56 PM, gawor@apache.org wrote:
> Geronimo Revision: 654010 built with tests included
>
> See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/build-0300.log
>
> Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 37 minutes 24 seconds
> [INFO] Finished at: Wed May 07 03:44:43 EDT 2008
> [INFO] Final Memory: 334M/703M
> [INFO]
> ------------------------------------------------------------------------
>
> TESTSUITE RESULTS (Failures only)
> =================================
> See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
>
> Assembly: tomcat
> =================================
> See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-tomcat/test.log
>
>
> Assembly: jetty
> =================================
> See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-jetty/test.log
>
>
> Samples: trunk
> =================================
> Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/samples-0300.log
>
> Build status: OK
>
Re: [BUILD] trunk: Successful
Posted by Jason Dillon <ja...@planet57.com>.
I will have a look, I've noticed a few other problems with the
testsuite which I'm trying to resolve too... as well as simplify the
configuration more if I can.
--jason
On May 7, 2008, at 9:11 PM, Jarek Gawor wrote:
> Ok. I see one weird problem with the testsuites now. For example, when
> I do "mvn install" in
> testsuite/webservices-testsuite/jaxb-tests/jaxb-client directory I see
> the following:
>
> ...
> [INFO] [surefire:test {execution: integration}]
> [INFO] Surefire report directory:
> /home/jgawor/development/geronimo/testsuite/webservices-testsuite/
> jaxb-tests/jaxb-client/target/surefire-reports
> [ERROR] There are test failures.
>
> Please refer to
> /home/jgawor/development/geronimo/testsuite/webservices-testsuite/
> jaxb-tests/jaxb-client/target/surefire-reports
> for the individual test results.
> [INFO] [geronimo:undeploy-module {execution: undeploy-client-as-
> moduleId}]
> ...
>
> The test case itself is not executed at all (despite what the error
> message says). However, the test case is executed properly if I add
> testng.xml file but that should not be necessary and used to work fine
> without it. Any ideas on this problem?
>
> Jarek
>
> On Wed, May 7, 2008 at 6:42 AM, Jason Dillon <ja...@planet57.com>
> wrote:
>> FYI, I changed the top-level testsuite module to use the shitty-
>> maven-plugin
>> to invoke the children *-testsuite modules, which forks off another
>> mvn
>> process for each and seems to hang less due to weird
>> ant/maven/groovy/whatever gremlins.
>>
>> I'm also doing a test now of using just one geronimo:start-server
>> (and
>> selenium bits) at the very top-level to see if that improves the
>> time to run
>> the testsuite... and doesn't cause weird problems.
>>
>> --jason
>>
>>
>>
>>
>> On May 7, 2008, at 3:56 PM, gawor@apache.org wrote:
>>
>>
>>> Geronimo Revision: 654010 built with tests included
>>>
>>> See the full build-0300.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/build-0300.log
>>>
>>> Download the binaries from
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507
>>> [INFO] BUILD SUCCESSFUL
>>> [INFO]
>> ------------------------------------------------------------------------
>>> [INFO] Total time: 37 minutes 24 seconds
>>> [INFO] Finished at: Wed May 07 03:44:43 EDT 2008
>>> [INFO] Final Memory: 334M/703M
>>> [INFO]
>> ------------------------------------------------------------------------
>>>
>>> TESTSUITE RESULTS (Failures only)
>>> =================================
>>> See detailed results at
>> http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
>>>
>>> Assembly: tomcat
>>> =================================
>>> See the full test.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-tomcat/test.log
>>>
>>>
>>> Assembly: jetty
>>> =================================
>>> See the full test.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-jetty/test.log
>>>
>>>
>>> Samples: trunk
>>> =================================
>>> Log:
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/samples-0300.log
>>>
>>> Build status: OK
>>>
>>>
>>
>>
Re: [BUILD] trunk: Successful
Posted by Jason Dillon <ja...@planet57.com>.
This should be fixed now. Though looks like there are some console
tests that are failing. One of which is the JMSServerTest, which is
failing because the page returned is missing some content due to this:
<snip>
INFO] 17:10:27,143 ERROR [JMSConnectorPortlet] Unable to render portlet
[INFO] java.lang.IllegalArgumentException: uri does not contain a
query part used for the name map
[INFO] at
org.apache.geronimo.gbean.AbstractName.<init>(AbstractName.java:121)
[INFO] at
org
.apache
.geronimo
.console
.jmsmanager.server.JMSConnectorPortlet.doView(JMSConnectorPortlet.java:
153)
[INFO] at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:
247)
[INFO] at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
[INFO] at
org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
[INFO] at
org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
[INFO] at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
[INFO] at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
[INFO] at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
[INFO] at
org
.apache
.geronimo
.jetty6
.InternalJettyServletHolder.handle(InternalJettyServletHolder.java:65)
[INFO] at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
[INFO] at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:
216)
[INFO] at
org
.apache
.geronimo
.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:
114)
[INFO] at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
[INFO] at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
[INFO] at
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
[INFO] at
org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access
$101(TwistyWebAppContext.java:40)
[INFO] at org.apache.geronimo.jetty6.handler.TwistyWebAppContext
$TwistyHandler.handle(TwistyWebAppContext.java:65)
[INFO] at
org
.apache
.geronimo
.jetty6
.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:
46)
[INFO] at
org
.apache
.geronimo
.jetty6
.handler.InstanceContextHandler.handle(InstanceContextHandler.java:67)
[INFO] at
org
.apache
.geronimo
.jetty6
.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48)
[INFO] at
org
.apache
.geronimo
.jetty6
.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
[INFO] at
org
.apache
.geronimo
.jetty6.handler.TwistyWebAppContext.handle(TwistyWebAppContext.java:59)
[INFO] at
org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:192)
[INFO] at
org
.apache
.pluto
.core
.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:
167)
[INFO] at
org
.apache
.pluto
.core
.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:
101)
[INFO] at
org
.apache
.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173)
[INFO] at
org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
[INFO] at
jsp
.WEB_002dINF
.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:87)
[INFO] at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
[INFO] at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
...
</snip>
I ran the steps manually and the box where input should be allowed is
not rendered, only this exception crapped out to the console... no
message on the console about the failure.
Would really be nice if the console reported problems back to the user
instead of just rendering empty pages...
:-(
--jason
On May 7, 2008, at 9:11 PM, Jarek Gawor wrote:
> Ok. I see one weird problem with the testsuites now. For example, when
> I do "mvn install" in
> testsuite/webservices-testsuite/jaxb-tests/jaxb-client directory I see
> the following:
>
> ...
> [INFO] [surefire:test {execution: integration}]
> [INFO] Surefire report directory:
> /home/jgawor/development/geronimo/testsuite/webservices-testsuite/
> jaxb-tests/jaxb-client/target/surefire-reports
> [ERROR] There are test failures.
>
> Please refer to
> /home/jgawor/development/geronimo/testsuite/webservices-testsuite/
> jaxb-tests/jaxb-client/target/surefire-reports
> for the individual test results.
> [INFO] [geronimo:undeploy-module {execution: undeploy-client-as-
> moduleId}]
> ...
>
> The test case itself is not executed at all (despite what the error
> message says). However, the test case is executed properly if I add
> testng.xml file but that should not be necessary and used to work fine
> without it. Any ideas on this problem?
>
> Jarek
>
> On Wed, May 7, 2008 at 6:42 AM, Jason Dillon <ja...@planet57.com>
> wrote:
>> FYI, I changed the top-level testsuite module to use the shitty-
>> maven-plugin
>> to invoke the children *-testsuite modules, which forks off another
>> mvn
>> process for each and seems to hang less due to weird
>> ant/maven/groovy/whatever gremlins.
>>
>> I'm also doing a test now of using just one geronimo:start-server
>> (and
>> selenium bits) at the very top-level to see if that improves the
>> time to run
>> the testsuite... and doesn't cause weird problems.
>>
>> --jason
>>
>>
>>
>>
>> On May 7, 2008, at 3:56 PM, gawor@apache.org wrote:
>>
>>
>>> Geronimo Revision: 654010 built with tests included
>>>
>>> See the full build-0300.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/build-0300.log
>>>
>>> Download the binaries from
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507
>>> [INFO] BUILD SUCCESSFUL
>>> [INFO]
>> ------------------------------------------------------------------------
>>> [INFO] Total time: 37 minutes 24 seconds
>>> [INFO] Finished at: Wed May 07 03:44:43 EDT 2008
>>> [INFO] Final Memory: 334M/703M
>>> [INFO]
>> ------------------------------------------------------------------------
>>>
>>> TESTSUITE RESULTS (Failures only)
>>> =================================
>>> See detailed results at
>> http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
>>>
>>> Assembly: tomcat
>>> =================================
>>> See the full test.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-tomcat/test.log
>>>
>>>
>>> Assembly: jetty
>>> =================================
>>> See the full test.log file at
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-jetty/test.log
>>>
>>>
>>> Samples: trunk
>>> =================================
>>> Log:
>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/samples-0300.log
>>>
>>> Build status: OK
>>>
>>>
>>
>>
Re: [BUILD] trunk: Successful
Posted by Jarek Gawor <jg...@gmail.com>.
Ok. I see one weird problem with the testsuites now. For example, when
I do "mvn install" in
testsuite/webservices-testsuite/jaxb-tests/jaxb-client directory I see
the following:
...
[INFO] [surefire:test {execution: integration}]
[INFO] Surefire report directory:
/home/jgawor/development/geronimo/testsuite/webservices-testsuite/jaxb-tests/jaxb-client/target/surefire-reports
[ERROR] There are test failures.
Please refer to
/home/jgawor/development/geronimo/testsuite/webservices-testsuite/jaxb-tests/jaxb-client/target/surefire-reports
for the individual test results.
[INFO] [geronimo:undeploy-module {execution: undeploy-client-as-moduleId}]
...
The test case itself is not executed at all (despite what the error
message says). However, the test case is executed properly if I add
testng.xml file but that should not be necessary and used to work fine
without it. Any ideas on this problem?
Jarek
On Wed, May 7, 2008 at 6:42 AM, Jason Dillon <ja...@planet57.com> wrote:
> FYI, I changed the top-level testsuite module to use the shitty-maven-plugin
> to invoke the children *-testsuite modules, which forks off another mvn
> process for each and seems to hang less due to weird
> ant/maven/groovy/whatever gremlins.
>
> I'm also doing a test now of using just one geronimo:start-server (and
> selenium bits) at the very top-level to see if that improves the time to run
> the testsuite... and doesn't cause weird problems.
>
> --jason
>
>
>
>
> On May 7, 2008, at 3:56 PM, gawor@apache.org wrote:
>
>
> > Geronimo Revision: 654010 built with tests included
> >
> > See the full build-0300.log file at
> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/build-0300.log
> >
> > Download the binaries from
> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507
> > [INFO] BUILD SUCCESSFUL
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Total time: 37 minutes 24 seconds
> > [INFO] Finished at: Wed May 07 03:44:43 EDT 2008
> > [INFO] Final Memory: 334M/703M
> > [INFO]
> ------------------------------------------------------------------------
> >
> > TESTSUITE RESULTS (Failures only)
> > =================================
> > See detailed results at
> http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
> >
> > Assembly: tomcat
> > =================================
> > See the full test.log file at
> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-tomcat/test.log
> >
> >
> > Assembly: jetty
> > =================================
> > See the full test.log file at
> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-jetty/test.log
> >
> >
> > Samples: trunk
> > =================================
> > Log:
> http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/samples-0300.log
> >
> > Build status: OK
> >
> >
>
>