Aha. Thanks Mohit. That was infra. Sorry about that. The first line in /etc/hosts said
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
Once I removed it, the tests started running faster. I'll update my patch to remove this particular test from timeout fix::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
On Wed, Feb 21, 2018 at 10:42 AM, Mohit Agrawal <moagrawa@xxxxxxxxxx> wrote:
Hi,I think as per test logs it is showing most of the taken by while test case is trying to mount a volume through nfswith a nolock option, i think it needs to be checked by nfs team why it is taking more time>>>>>>>>>>>>>>>>>>>>>>>>>>>>sudo grep -i "mount_nfs" -A 1 d-backends-patchy.log[2018-02-21 04:55:56.466891]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 17 mount_nfs builder500.cloud.gluster.org:/ patchy /mnt/nfs/0 nolock ++++++++++ [2018-02-21 04:55:59.496667]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 18 Y force_umount /mnt/nfs/0 ++++++++++ --[2018-02-21 04:56:24.943041]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 25 mount_nfs localhost:/patchy /mnt/nfs/0 nolock ++++++++++ [2018-02-21 04:58:29.986140]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 26 Y force_umount /mnt/nfs/0 ++++++++++ --[2018-02-21 04:58:54.419774]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 32 ! mount_nfs localhost:/patchy /mnt/nfs/0 nolock ++++++++++ [2018-02-21 05:00:59.463965]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 33 gluster --mode=script --wignore volume reset patchy force ++++++++++ --[2018-02-21 05:01:19.095653]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 39 ! mount_nfs localhost:/patchy /mnt/nfs/0 nolock ++++++++++ [2018-02-21 05:03:24.150833]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 42 gluster --mode=script --wignore volume set patchy nfs.rpc-auth-reject 192.168.1.1 ++++++++++ --[2018-02-21 05:03:44.550737]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 45 mount_nfs localhost:/patchy /mnt/nfs/0 nolock ++++++++++ [2018-02-21 05:05:49.595573]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 46 Y force_umount /mnt/nfs/0 ++++++++++ --[2018-02-21 05:06:15.297241]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 57 mount_nfs localhost:/patchy /mnt/nfs/0 nolock ++++++++++ [2018-02-21 05:08:20.341869]:++++++++++ G_LOG:./tests/bugs/rpc/bug-921072.t: TEST: 58 Y force_umount /mnt/nfs/0 ++++++++++ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>. RegardsMohit AgrawalOn Wed, Feb 21, 2018 at 9:52 AM, Raghavendra Gowdappa <rgowdapp@xxxxxxxxxx> wrote:+Mohit.On Wed, Feb 21, 2018 at 7:47 AM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:[20:24:39] Running tests in file ./tests/bugs/rpc/bug-921072.t ./tests/bugs/rpc/bug-921072.t timed out after 200 seconds ./tests/bugs/rpc/bug-921072.t: bad status 124This is just one of the instances, but I have seen this test failing in last 3-4 days at least 10 times.Unfortunately, it doesn't look like the regression actually passes in mainline for any of the patches atm.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
--
nigelb
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel