I took a look at the failure. The java Messenger impl seems to be hanging
on the new test before it even gets to the asserts that have anything to do
with the bug. I fixed the test harness so that it no longer hangs, but it
is still timing out and I'm not really familiar enough with the java
Messenger code to figure out why.


On Fri, May 10, 2013 at 10:04 AM, Phil Harvey <p...@philharveyonline.com>wrote:

> Hi,
> The following commit made on Wednesday is causing the proton-j Jenkins job
> to fail:
> *Revision 1480445<
> http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1480445>by
> rhs <https://builds.apache.org/user/rhs/>: *
> PROTON-295 <https://issues.apache.org/jira/browse/PROTON-295>: decoupled
> tracking of store entries from put/get of store entries, fixed tracking of
> incoming entries to start when they are returned via get rather than when
> they are read off of the wire
> See: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/334/
> Is anyone who is familiar with this change available to fix it please?
> I recommend that folks subscribe to Jenkins build notifications emails so
> they are aware when their commits break the build.
> Thanks
> Phil

Reply via email to