On 2014-07-09 22:39, Harshavardhana wrote:
I thought pkg-version in build-aux should have fixed this properly?
Well, it does generate correct ascending names, but since 'git describe'
picks up the v3.5qa2 tag, new package names are based on that (and hence
yum considers 3.5.1 newer than
On Wed, Jul 09, 2014 at 09:33:01PM +0100, Justin Clift wrote:
That v3.5qa2 tag name on master is annoying, due to the RPM
naming it causes when building on master.
Did we figure out a solution?
Maybe we should do a v3.6something tag at feature freeze
time or something?
I think we can
On 07/08/2014 01:54 PM, Avra Sengupta wrote:
In the test case, we are checking gluster snap status to see if all the
bricks are alive. One of the snap bricks fail to start up, and hence we
see the failure. The brick fails to bind with Address already in use
error. But if we see clearly that same
Looks like Rackspace had some issues during one of their upgrades
or something, and two of the slave VMs permanently died:
* slave20
* slave22
Those VMs have been nuked and new VMs built to take their place
(same names).
Any logs that were on the old VMs are no longer available,
having also
hi,
I wanted to document the core data structres and debugging infra
in gluster. This is the first patch in that series. Please review and
provide comments.
I am not very familiar with iobuf infra. Please feel free to provide
comments in the patch for that section as well. I can amend
On Thu, Jul 10, 2014 at 05:14:08PM +0530, Vijay Bellur wrote:
On 07/08/2014 01:54 PM, Avra Sengupta wrote:
In the test case, we are checking gluster snap status to see if all the
bricks are alive. One of the snap bricks fail to start up, and hence we
see the failure. The brick fails to bind
On 10/07/2014, at 1:41 PM, Niels de Vos wrote:
On Thu, Jul 10, 2014 at 05:14:08PM +0530, Vijay Bellur wrote:
snip
A lot of regression runs are failing because of this test unit.
Given feature freeze is around the corner, shall we provide a +1
verified manually for those patchsets that fail
On 07/09/2014 12:11 AM, Gluster Build System wrote:
SRC:
http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.5beta2.tar.gz
This release is made off jenkins-release-80
-- Gluster Build System
___
Gluster-devel mailing list
This sounds perfect.
On Thu, Jul 10, 2014 at 2:15 PM, Niels de Vos nde...@redhat.com wrote:
On Wed, Jul 09, 2014 at 09:33:01PM +0100, Justin Clift wrote:
That v3.5qa2 tag name on master is annoying, due to the RPM
naming it causes when building on master.
Did we figure out a solution?
On 07/10/2014 02:23 PM, Justin Clift wrote:
On 10/07/2014, at 9:45 AM, Niels de Vos wrote:
On Wed, Jul 09, 2014 at 09:33:01PM +0100, Justin Clift wrote:
That v3.5qa2 tag name on master is annoying, due to the RPM
naming it causes when building on master.
Did we figure out a solution?
Maybe
Hi All,
1) Tried reproducing the issue in local setup by running the regression test
multiple times in a for loop. But the issue never hit!
2) As Avra pointed out the logs suggests that the port(49159) assigned by the
glusterd(host1) to the snap brick is already in use by some other process
3)
On 10/07/2014, at 2:27 PM, Joseph Fernandes wrote:
Hi All,
1) Tried reproducing the issue in local setup by running the regression test
multiple times in a for loop. But the issue never hit!
2) As Avra pointed out the logs suggests that the port(49159) assigned by the
glusterd(host1) to
Sent a patch that temporarily disables the failing TEST
http://review.gluster.org/#/c/8259/
- Original Message -
From: Joseph Fernandes josfe...@redhat.com
To: Justin Clift jus...@gluster.org
Cc: Niels de Vos nde...@redhat.com, Gluster Devel
gluster-devel@gluster.org, Vijay Bellur
On 10/07/2014, at 12:44 PM, Vijay Bellur wrote:
snip
A lot of regression runs are failing because of this test unit. Given feature
freeze is around the corner, shall we provide a +1 verified manually for
those patchsets that fail this test?
Went through and did this manually, as Gluster
hi Harsha,
Know anything about the following warnings on latest master?
In file included from msg-nfs3.h:20:0,
from msg-nfs3.c:22:
nlm4-xdr.h:6:14: warning: extra tokens at end of #ifndef directive
[enabled by default]
#ifndef _NLM4-XDR_H_RPCGEN
^
Do not know, they do not show up locally on my laptop, can you point
me to a build so that i can investigate?
On Thu, Jul 10, 2014 at 6:45 PM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
hi Harsha,
Know anything about the following warnings on latest master?
In file included from
On Thu, Jul 10, 2014 at 7:30 PM, Harshavardhana
har...@harshavardhana.net wrote:
Do not know, they do not show up locally on my laptop, can you point
me to a build so that i can investigate?
I think these are related to C99 standards, are you using clang? -
this must be xdrgen bug that it
17 matches
Mail list logo
