On Tue, Aug 17, 2010 at 11:59 AM, Stefan Bodewig <bode...@apache.org> wrote: > On 2010-08-17, Rahul Akolkar wrote: > >> On Mon, Aug 16, 2010 at 4:53 PM, Stefan Bodewig <bode...@apache.org> wrote: >>> On 2010-08-16, Rahul Akolkar wrote: > >>>> For the two scxml test failures, there is no such usage. I think I'll >>>> let things settle some before taking a look. > >>> No, for scxml things are different. Until last week Gump didn't build >>> scxml (or Sanselan, or Proxy for that matter) and it failed right from >>> the start (as did Sanselan) after I added it. > >> OK, both failing tests involve use of Commons EL (and thereby, have a >> dependency on Servlet 2.4 and JSP 2.0) > > These should be the version form the mvn repo scxml asks for, Gump > doesn't inject the Servlet jars. > >> is there a way to look at the surefire reports in the workspace >> through the web interface? > > Yes, if Gump's metadata says so (in scxml's case it does). Right now > vmgump has a few memory issues so I'll use the Solaris zone for the > URLs. > > If you go to the failing project's page > <http://gump.zones.apache.org/gump/test/apache-commons/commons-scxml-test/index.html> > and scroll to the bottom there are links to the surefire reports. For > example > <http://gump.zones.apache.org/gump/test/apache-commons/commons-scxml-test/gump_file/org.apache.commons.scxml.model.ModelTestSuite.txt.html> > <snip/>
Yes, thanks, that will help when I try to debug. So the trick seems to be to use the zone URLs and not the ones in the nag (perhaps until said memory issues are resolved). For example, the last nag [1] that got sent out contained these two URLs [2, 3] of relevance, and I wasn't able to navigate to the surefire reports from either of those. -Rahul [1] http://markmail.org/message/s6w3vud27qi4kx72 [2] http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/index.html [3] http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
