On 02/28/2013 09:49 AM, Alan Conway wrote:
On 02/27/2013 06:31 PM, Keith W wrote:
On 27 February 2013 22:28, Alan Conway acon...@redhat.com wrote:
On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote:
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent PROTON-215 commits.
The failing test is:
On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote:
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent PROTON-215 commits.
The failing test is:
notificati...@qpid.apache.org
-- Rob
On 27 February 2013 21:51, Alan Conway acon...@redhat.com wrote:
On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote:
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent PROTON-215 commits.
The failing test is:
On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote:
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent PROTON-215 commits.
The failing test is:
On 27 February 2013 23:28, Alan Conway acon...@redhat.com wrote:
On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote:
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent PROTON-215 commits.
The failing test is:
On 27 February 2013 22:28, Alan Conway acon...@redhat.com wrote:
On Wed, 2013-02-27 at 11:19 +, Phil Harvey wrote:
Hi,
I notice that proton-jni on Jenkins is failing [1] , probably due to the
recent PROTON-215 commits.
The failing test is:
