You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by Apache Hudson Server <hu...@hudson.apache.org> on 2011/03/16 21:20:40 UTC

Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1486

See <https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1486/changes>

RE: Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1486

Posted by Jukka Zitting <jz...@adobe.com>.

Hi,

That's yet another lock expiration test failure. :-( I still haven't had time to really focus on that one.

BR,

Jukka Zitting

-----Original Message-----
From: Apache Hudson Server [mailto:hudson@hudson.apache.org] 
Sent: Wednesday, March 16, 2011 9:21 PM
To: dev@jackrabbit.apache.org
Subject: Jenkins build became unstable: Jackrabbit-trunk » Jackrabbit Core #1486

See <https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1486/changes>

Jenkins build is back to stable : Jackrabbit-trunk » Jackrabbit Core #1487

Posted by Apache Hudson Server <hu...@hudson.apache.org>.

See <https://hudson.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1487/>