[Gluster-devel] State of 3.7 regression

2016-05-02 Thread Raghavendra Talur
Hi All, I had sent a patch to backport all the test infra and test fixes to 3.7 branch from master.[1] Here are the details for test failures 1. Netbsd 01:32:03 1 test(s) failed 01:32:03 ./tests/basic/afr/durability-off.t 01:32:03 01:32:03 1 test(s) generated core 01:32:03

Re: [Gluster-devel] Bitrot Review Request

2016-05-02 Thread Pranith Kumar Karampuri
On Fri, Apr 29, 2016 at 12:37 PM, Kotresh Hiremath Ravishankar < khire...@redhat.com> wrote: > Hi Pranith, > > You had a concern of consuming I/O threads when bit-rot uses rchecksum > interface to > signing, normal scrubbing and on-demand scrubbing with tiering. > > >

Re: [Gluster-devel] Improve EXPECT/EXPECT_WITHIN result check in tests

2016-05-02 Thread Niels de Vos
On Mon, May 02, 2016 at 01:49:08PM +0200, Xavier Hernandez wrote: > Hi, > > I've found an spurious failure caused by an incorrect check of the expected > value in EXPECT_WITHIN. > > The problem is that the value passed to EXPECT_WITHIN (EXPECT also has the > same problem) is considered a regular

Re: [Gluster-devel] Improve EXPECT/EXPECT_WITHIN result check in tests

2016-05-02 Thread Jeff Darcy
> Would it be ok to change all regular expression checks to something like > this in include.rc ? > > if [[ "$a" =~ ^$e$ ]]; then > > This will allow using regular expressions in EXPECT and EXPECT_WITHIN, > but will enforce full answer match in all cases, avoiding some possible > side

[Gluster-devel] Improve EXPECT/EXPECT_WITHIN result check in tests

2016-05-02 Thread Xavier Hernandez
Hi, I've found an spurious failure caused by an incorrect check of the expected value in EXPECT_WITHIN. The problem is that the value passed to EXPECT_WITHIN (EXPECT also has the same problem) is considered a regular expression but most tests do not pass a full/valid regular expression.

Re: [Gluster-devel] Exporting Gluster Volume

2016-05-02 Thread ABHISHEK PALIWAL
Hi Niels, Here is the output of rpcinfo -p $NFS_SERVER root@128:/# rpcinfo -p $NFS_SERVER program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper

[Gluster-devel] arbiter.t failure

2016-05-02 Thread Raghavendra Gowdappa
https://build.gluster.org/job/rackspace-regression-2GB-triggered/20354/console This seems like a spurious failure as the patch seems unrelated to failure. regards, Raghavendra ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Exporting Gluster Volume

2016-05-02 Thread Niels de Vos
On Mon, May 02, 2016 at 04:14:01PM +0530, ABHISHEK PALIWAL wrote: > HI Team, > > I am exporting gluster volume using GlusterNFS with ACL support but at NFS > client while running 'setfacl' command getting "setfacl: /tmp/e: Remote I/O > error" > > > Following is the NFS option status for

[Gluster-devel] Exporting Gluster Volume

2016-05-02 Thread ABHISHEK PALIWAL
HI Team, I am exporting gluster volume using GlusterNFS with ACL support but at NFS client while running 'setfacl' command getting "setfacl: /tmp/e: Remote I/O error" Following is the NFS option status for Volume: nfs.enable-ino32 no nfs.mem-factor 15 nfs.export-dirs on nfs.export-volumes on

[Gluster-devel] Synctask memory corruption in NetBSD

2016-05-02 Thread Manikandan Selvaganesh
Hi, There are some quota related tests that are failing in NetBSD. We had a look at the core files that the test has generated. Apparently, it is failing in synctask framework. Marker uses synctask framework a lot and the stack size that we use in marker is 16k. Here is the stack trace: #0

Re: [Gluster-devel] Requesting for a NetBSD setup

2016-05-02 Thread Emmanuel Dreyfus
On Mon, May 02, 2016 at 01:55:43PM +0530, Manikandan Selvaganesh wrote: > Could you please provide us a NetBSD machine as the test cases are failing > and we need to have a look on it? nbslave72.cloud.gluster.org was put offline for some jenkins breakage that todes not seems to be slave-related:

[Gluster-devel] Requesting for a NetBSD setup

2016-05-02 Thread Manikandan Selvaganesh
Hi all, Could you please provide us a NetBSD machine as the test cases are failing and we need to have a look on it? https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16439/consoleFull https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16440/console --

Re: [Gluster-devel] ./tests/basic/tier/new-tier-cmds.t failing on master branch

2016-05-02 Thread Hari Gowtham
Hi, I'll take a look at it. - Original Message - > From: "Dan Lambright" > To: "RHGS tiering mailing list" > Sent: Monday, May 2, 2016 4:56:24 AM > Subject: Re: [Gluster-devel] ./tests/basic/tier/new-tier-cmds.t failing on > master