Description of problem: This test fails more than often, in regression jobs as well in my local setup. root@6df17a761d85:/home/glusterfs# prove -vf tests/bugs/distribute/bug-1122443.t tests/bugs/distribute/bug-1122443.t .. 1..12 ok 1, LINENUM:34 ok 2, LINENUM:35 ok 3, LINENUM:37 ok 4, LINENUM:38 ok 5, LINENUM:41 ok 6, LINENUM:42 ok 7, LINENUM:48 ok 8, LINENUM:49 ok 9, LINENUM:50 ok 10, LINENUM:51 ok 11, LINENUM:54 not ok 12 , LINENUM:58 FAILED COMMAND: [ /mnt/glusterfs/0/subdir/special_b:0,/mnt/glusterfs/0/subdir/special_c:0,/mnt/glusterfs/0/subdir/special_p:0,/mnt/glusterfs/0/subdir/special_u:0,/mnt/glusterfs/0/subdir/symlink:0, == /mnt/glusterfs/0/subdir/special_b:2,/mnt/glusterfs/0/subdir/special_c:3,/mnt/glusterfs/0/subdir/special_p:5,/mnt/glusterfs/0/subdir/special_u:4,/mnt/glusterfs/0/subdir/symlink:1, ] Failed 1/12 subtests Test Summary Report ------------------- tests/bugs/distribute/bug-1122443.t (Wstat: 0 Tests: 12 Failed: 1) Failed test: 12 Files=1, Tests=12, 10 wallclock secs ( 0.03 usr 0.01 sys + 0.60 cusr 0.77 csys = 1.41 CPU) Result: FAIL root@6df17a761d85:/home/glusterfs# prove -vf tests/bugs/distribute/bug-1122443.t tests/bugs/distribute/bug-1122443.t .. 1..12 ok 1, LINENUM:34 ok 2, LINENUM:35 ok 3, LINENUM:37 ok 4, LINENUM:38 ok 5, LINENUM:41 ok 6, LINENUM:42 ok 7, LINENUM:48 ok 8, LINENUM:49 ok 9, LINENUM:50 ok 10, LINENUM:51 ok 11, LINENUM:54 not ok 12 , LINENUM:58 FAILED COMMAND: [ /mnt/glusterfs/0/subdir/special_b:0,/mnt/glusterfs/0/subdir/special_c:0,/mnt/glusterfs/0/subdir/special_p:0,/mnt/glusterfs/0/subdir/special_u:0,/mnt/glusterfs/0/subdir/symlink:0, == /mnt/glusterfs/0/subdir/special_b:2,/mnt/glusterfs/0/subdir/special_c:3,/mnt/glusterfs/0/subdir/special_p:5,/mnt/glusterfs/0/subdir/special_u:4,/mnt/glusterfs/0/subdir/symlink:1, ] Failed 1/12 subtests Test Summary Report ------------------- tests/bugs/distribute/bug-1122443.t (Wstat: 0 Tests: 12 Failed: 1) Failed test: 12 Files=1, Tests=12, 18 wallclock secs ( 0.02 usr 0.01 sys + 0.50 cusr 0.64 csys = 1.17 CPU) Result: FAIL https://review.gluster.org/#/c/20584 had nothing to do with this test, however it has failed almost in all the regression attempts. An email https://lists.gluster.org/pipermail/gluster-devel/2018-July/055073.html was sent, but haven't seen any actions. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20595 (tests: mark tests/bugs/distribute/bug-1122443.t a bad test) posted (#1) for review on master by Atin Mukherjee
Not a spurious failure. This is a bug introduced by commit 7131de81f72dda0ef685ed60d0887c6e14289b8c With the latest master, I created a single brick volume and some files inside it.The first call to ls -l returns Null iatt information. This test uses this information to check if the operation succeeded and hence it fails. [root@rhgs313-6 ~]# umount -f /mnt/fuse1; mount -t glusterfs -s server1:/vol1 /mnt/fuse1; ls -l /mnt/fuse1/; echo "Trying again"; ls -l /mnt/fuse1 total 0 ----------. 0 root root 0 Jan 1 1970 file-1 ----------. 0 root root 0 Jan 1 1970 file-2 ----------. 0 root root 0 Jan 1 1970 file-3 ----------. 0 root root 0 Jan 1 1970 file-4 ----------. 0 root root 0 Jan 1 1970 file-5 d---------. 0 root root 0 Jan 1 1970 subdir Trying again total 3 -rw-r--r--. 1 root root 33 Aug 3 14:06 file-1 -rw-r--r--. 1 root root 33 Aug 3 14:06 file-2 -rw-r--r--. 1 root root 33 Aug 3 14:06 file-3 -rw-r--r--. 1 root root 33 Aug 3 14:06 file-4 -rw-r--r--. 1 root root 33 Aug 3 14:06 file-5 d---------. 0 root root 0 Jan 1 1970 subdir [root@rhgs313-6 ~]# The above works as expected if I revert this commit.
This is fixed as another patch from Mohit. Not seen in a long time.