On Tue, Jul 11, 2017 at 3:52 PM, Csaba Henk wrote:
> I also noticed this, searching on the issue had me landed on this thread.
>
> I just have one extra concern: why are the links that are provided at the
> bottom of the console log to core&binaries and logs are broken?
>
Just take out 'archives
I also noticed this, searching on the issue had me landed on this thread.
I just have one extra concern: why are the links that are provided at the
bottom of the console log to core&binaries and logs are broken?
Csaba
On Fri, Jul 7, 2017 at 6:07 AM, Atin Mukherjee wrote:
> https://build.gluster
On Fri, Jul 07, 2017 at 07:42:08AM -0400, Jeff Darcy wrote:
>
>
> On Fri, Jul 7, 2017, at 03:36 AM, Niels de Vos wrote:
> > The segfault is caused by GF_ASSERT() on
> > https://review.gluster.org/#/c/17662/2/libglusterfs/src/mem-pool.c@563 .
> > At the moment I'm not sure how this can happen, unl
On Fri, Jul 7, 2017, at 03:36 AM, Niels de Vos wrote:
> The segfault is caused by GF_ASSERT() on
> https://review.gluster.org/#/c/17662/2/libglusterfs/src/mem-pool.c@563 .
> At the moment I'm not sure how this can happen, unless glfs_fini() is
> called more than once on a glfs_t object.
It's bec
On Fri, Jul 07, 2017 at 09:37:35AM +0530, Atin Mukherjee wrote:
> https://build.gluster.org/job/netbsd7-regression/4761/consoleFull
mem_pool_fini() has recently been added. It suggests that there is a
problem with the implementation, maybe not NetBSD specific.
From the test console log:
[01:24:1
https://build.gluster.org/job/netbsd7-regression/4761/consoleFull
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel
