abdera-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Evans" <objective...@gmail.com>
Subject Re: Building the trunk
Date Sat, 28 Jul 2007 03:21:05 GMT
Ah, okay. I started making a patch that would move this test into
/src/test/it but I can't seem to make eclipse and svn plugin behave.
In any event, I'll assume that one of the commiters will move/remove
the offending test when they can.

--Rob Evans

On 7/27/07, James M Snell <jasnell@gmail.com> wrote:
> Actually, it would appear that the verisign endpoint is no longer
> functioning correctly.  The point of this test was to check interop with
> signed entries.  So far, Abdera is pretty much the only Atom library out
> there I know of that supports dsig's.  For now, we need to just go ahead
> and disable this test.
>
> - James
>
> Rob Evans wrote:
> > The maven build is almost working perfectly. I just pulled down the
> > trunk and issued a: mvn install
> >
> > The build fails with:
> >
> > Failed tests:
> >   testThirdPartyVerification(org.apache.abdera.test.security.DSigThirdPartyVerifyTest)
> >
> >
> > I modified the assertTrue() statement to assertSame() and I get:
> >
> >       junit.framework.AssertionFailedError: expected same:<200> was not:<502>
> >       at junit.framework.Assert.fail(Assert.java:47)
> >       at junit.framework.Assert.failNotSame(Assert.java:276)
> >       ...
> >
> > Seems we are hitting "http://verisignlabs.com/tg/verify" and getting a
> > 502 Bad Gateway response.
> >
> > Presumably this unit test was written for a reason, so I would not
> > want to see it removed. On the other hand, it doesn't seem right that
> > it should be able to break the build. I think maven supports the
> > notion of integration tests. Perhaps the tests that depend on external
> > systems should be moved to a separate directory so that they can't
> > break a build but they can still get run, say, before actually cutting
> > a release.
> >
> > Thoughts?
> >
> >
> >
> >
> >
> >
> > On 7/26/07, James M Snell <jasnell@gmail.com> wrote:
> >> I just checked in a fix that should resolve this.
> >>
> >> - James
> >>
> >> Adam Constabaris wrote:
> >>> I'm seeing this too.  I notice that the ant build doesn't run any tests
> >>> in the server module, while Maven does; that's possibly why this doesn't
> >>> show up for ant users.
> >>>
> >>> I got some distance with tracking down the problem, but life intervened.
> >>>  So here's the (relevant, IMO) parts of the stack trace:
> >>>
> >>> java.lang.NullPointerException
> >>>         at
> >>> org.apache.abdera.protocol.server.ServiceManager.newServiceContext(Se
> >>> rviceManager.java:69)
> >>>
> >>> NPE is thrown by the final line of the following snippet:
> >>>
> >>> === ServiceManager ===
> >>>
> >>> ServiceContext context =
> >>>       (ServiceContext) ServiceUtil.newInstance(
> >>>         SERVICE_CONTEXT,
> >>>         (instance != null) ?
> >>>           instance :
> >>>           DefaultServiceContext.class.getName(),
> >>>         abdera);
> >>>     log.debug(Messages.format("INITIALIZING.INSTANCE", "ServiceContext"));
> >>>     context.init(abdera, properties);
> >>>
> >>> =====================
> >>>
> >>> I got this far: instance, which should be the name of the implementing
> >>> class, is null, so we should be getting a DefaultServiceContext
> >>> instance, but that doesn't happen.  The ServiceUtil.newInstance method
> >>> silently returns null, and that's where I had to stop looking; I'm not
> >>> sure whether it should throw an exception of some sort here, or whether
> >>> the client code in ServiceManager should check.
> >>>
> >>>
> >>> AC
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Rob Evans wrote:
> >>>
> >>>> Lastly, I've been seeing build failures. I'll try to track down the
> >>>> root cause and, if its really a problem with the codebase and not my
> >>>> build system, I'll submit a bug.
> >>>>
> >>>> -------------------------------------------------------
> >>>> T E S T S
> >>>> -------------------------------------------------------
> >>>> Running org.apache.abdera.test.server.UtilityTest
> >>>> Tests run: 5, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.344
> >>>> sec <<< FAILURE!
> >>>>
> >>>> Results :
> >>>>
> >>>> Tests in error:
> >>>>  testServiceManager(org.apache.abdera.test.server.UtilityTest)
> >>>>  testRegexTargetResolver(org.apache.abdera.test.server.UtilityTest)
> >>>>  testSubjectResolver(org.apache.abdera.test.server.UtilityTest)
> >>>>
> >>>> Tests run: 5, Failures: 0, Errors: 3, Skipped: 0
> >>>>
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> [ERROR] BUILD FAILURE
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> [INFO] There are test failures.
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> [INFO] For more information, run Maven with the -e switch
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>> [INFO] Total time: 1 minute 49 seconds
> >>>> [INFO] Finished at: Thu Jul 26 11:05:13 PDT 2007
> >>>> [INFO] Final Memory: 12M/29M
> >>>> [INFO]
> >>>> ------------------------------------------------------------------------
> >>>>
> >>>> robevans@robevans-wxp01 ~/workspaces/abdera/abdera.trunk
> >>>> $ mvn install
> >>>
> >
>

Mime
View raw message