Am facing the same issue on patches
http://review.gluster.org/#/c/10313/ and
http://review.gluster.org/#/c/10588/. The netbsd regression passes for
both of them http://build.gluster.org/job/netbsd6-smoke/6065/console and
http://build.gluster.org/job/netbsd6-smoke/6076/console, but the results
Hi,
I have run NetBSD regression on http://review.gluster.org/#/c/10358/
twice. http://build.gluster.org/job/netbsd6-smoke/6066/console and
http://build.gluster.org/job/netbsd6-smoke/6135/console. Both the times
the regressions have passed but the results are not getting reflected in
the patc
Core was generated by `glusterd --xlator-option *.upgrade=on -N'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f489c747c3b in ?? ()
I would like to provide debug info and installed
glusterfs-debuginfo-3.8dev-0.58.gitf692757.el7.centos.x86_64, but I'm
getting:
Missing s
Hi,
I did a local sparse image copy benchmark copying from a gluster mount
(of a local gluster-server) vs copying directly from the gluster-brick
to test SEEK_HOLE support and performance.
Motivation : VM's image files are sparse.
Benchmark:
cp /mnt/gluster-mount/image to /tmp/
=> takes
On 05/09/2015 12:45 AM, Vijay Bellur wrote:
Hi All,
Thanks to all our efforts, we are inching closer towards 3.7.0. Here is
the updated release schedule for 3.7.0:
1. Patch merge deadline and beta2 tagging - 1600 UTC 05/09
2. Final test window starts at 1600 UTC 05/09
Update: We are pushing
On 05/09/2015 04:23 PM, Kotresh Hiremath Ravishankar wrote:
> Hi,
>
> There are few regression failures with changelog translator init being failed
> and a core is generated
> as explained below.
>
> 1. Why changelog translator init failed?
>
> In snapshot test cases, virtual multiple
On 05/09/2015 04:23 PM, Krishnan Parthasarathi wrote:
Oh nice, I might have missed the mails. Do you mind sharing the plan for
4.0? Any reason why you guys do not want to continue glusterd as
translator model?
I don't understand why we are using the translator model in the first place.
I guess
> Oh nice, I might have missed the mails. Do you mind sharing the plan for
> 4.0? Any reason why you guys do not want to continue glusterd as
> translator model?
I don't understand why we are using the translator model in the first place.
I guess it was to reuse rpc code. You should be able to sh
Hi,
There are few regression failures with changelog translator init being failed
and a core is generated
as explained below.
1. Why changelog translator init failed?
In snapshot test cases, virtual multiple peers are setup in single node,
which causes 'Address already in use' and 'p
On 05/09/2015 03:04 PM, Kaushal M wrote:
Modularising GlusterD is something we plan to do. As of now, it's
just that a plan. We don't yet have a design to achieve it yet.
What Atin mentioned and what you've mentioned seem to be the same at a
high level. The core of GlusterD will be a co-ordina
comments inline
- Original Message -
From: "Gaurav Garg"
To: "Atin Mukherjee"
Cc: "Gluster Devel"
Sent: Saturday, May 9, 2015 3:25:48 PM
Subject: Re: [Gluster-devel] regression failure in
tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-info.t
Thanx atin for this fix
On 05/09/2015 03:19 PM, Krishnan Parthasarathi wrote:
Why not break glusterd into small parts and distribute the load to
different people? Did you guys plan anything for 4.0 for breaking glusterd?
It is going to be a maintenance hell if we don't break it sooner.
Good idea. We have thought about
Thanx atin for this fix.
~gaurav.
- Original Message -
From: "Atin Mukherjee"
To: "ggarg >> Gaurav Garg"
Cc: "Gluster Devel"
Sent: Saturday, May 9, 2015 12:28:42 PM
Subject: Re: [Gluster-devel] regression failure in
tests/bugs/bitrot/1209752-volume-status-should-show-bitrot-scrub-inf
> Why not break glusterd into small parts and distribute the load to
> different people? Did you guys plan anything for 4.0 for breaking glusterd?
> It is going to be a maintenance hell if we don't break it sooner.
Good idea. We have thought about it. Just re-architecting glusterd doesn't
(and wi
Modularising GlusterD is something we plan to do. As of now, it's
just that a plan. We don't yet have a design to achieve it yet.
What Atin mentioned and what you've mentioned seem to be the same at a
high level. The core of GlusterD will be a co-ordinating engine, which
defines an interface for
On 05/09/2015 02:21 PM, Atin Mukherjee wrote:
On 05/09/2015 01:36 PM, Pranith Kumar Karampuri wrote:
On 05/09/2015 11:08 AM, Krishnan Parthasarathi wrote:
Ah! now I understood the confusion. I never said maintainer should fix
all the bugs in tests. I am only saying that they maintain tests, j
On 05/09/2015 01:36 PM, Pranith Kumar Karampuri wrote:
>
> On 05/09/2015 11:08 AM, Krishnan Parthasarathi wrote:
>>> Ah! now I understood the confusion. I never said maintainer should fix
>>> all the bugs in tests. I am only saying that they maintain tests, just
>>> like we maintain code. Whethe
On Fri, May 08, 2015 at 05:55:01PM +0800, Paul Guo wrote:
> Hi,
>
> gdb debugging shows the rootcause seems to be quite straightforward. The
> gluster version is 3.4.5 and the stack:
As others have mentioned already, GlusterFS 3.4 is on its way out. When
3.7.0 has been released (any day now), the
On 05/09/2015 11:08 AM, Krishnan Parthasarathi wrote:
Ah! now I understood the confusion. I never said maintainer should fix
all the bugs in tests. I am only saying that they maintain tests, just
like we maintain code. Whether you personally work on it or not, you at
least have an idea of what i
It is crashing in libgcc!!!
Program terminated with signal 11, Segmentation fault.
#0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.149.el6_6.7.x86_64 keyutils-libs-1.4-5.el6.x86_64
krb5-libs-1.10.3-37.el6_6.x86_64 libcom
On 05/09/2015 12:49 PM, Kotresh Hiremath Ravishankar wrote:
If you observe the logs below. Socket binding failed because of Address and
port already in use ERROR.
Because of that changelog failed to initiate rpc server, hence failed.
Not sure why socket binding failed in this machine.
[2015-05-
If you observe the logs below. Socket binding failed because of Address and
port already in use ERROR.
Because of that changelog failed to initiate rpc server, hence failed.
Not sure why socket binding failed in this machine.
[2015-05-08 21:34:47.747059] E [socket.c:823:__socket_server_bind]
0-s
One more from quota
http://build.gluster.org/job/rackspace-regression-2GB-triggered/8901/consoleFull
~Atin
On 05/08/2015 03:47 PM, Atin Mukherjee wrote:
> http://build.gluster.org/job/rackspace-regression-2GB-triggered/8782/consoleFull
>
> Failed test case : tests/bugs/replicate/bug-976800.t
>
23 matches
Mail list logo
