On 17 May 2015, at 13:36, Vijay Bellur vbel...@redhat.com wrote:
On 05/17/2015 02:32 PM, Vijay Bellur wrote:
[Adding gluster-devel]
On 05/16/2015 11:31 PM, Niels de Vos wrote:
On Sat, May 16, 2015 at 06:32:00PM +0200, Niels de Vos wrote:
It seems that many failures of the regression tests (at
Vijay Bellur vbel...@redhat.com wrote:
Around 9:25 UTC.
There is this one that looks like the old bug:
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/5410/console
But the same machine (nbslave71) was at least able to run other jobs after this.
--
Emmanuel Dreyfus
On Sun, May 17, 2015 at 06:06:19PM +0530, Vijay Bellur wrote:
On 05/17/2015 02:32 PM, Vijay Bellur wrote:
[Adding gluster-devel]
On 05/16/2015 11:31 PM, Niels de Vos wrote:
On Sat, May 16, 2015 at 06:32:00PM +0200, Niels de Vos wrote:
It seems that many failures of the regression tests (at
Another connectivity failure:
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/5420
The slave VM uptime sugests it did not reboot during the build.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-devel
On 05/17/2015 02:32 PM, Vijay Bellur wrote:
[Adding gluster-devel]
On 05/16/2015 11:31 PM, Niels de Vos wrote:
On Sat, May 16, 2015 at 06:32:00PM +0200, Niels de Vos wrote:
It seems that many failures of the regression tests (at least for
NetBSD) are caused by failing to reconnect to the
