[Bugs] [Bug 1696633] New: GlusterFs v4.1.5 Tests from /tests/bugs/ module failing on Intel

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1696633

            Bug ID: 1696633
           Summary: GlusterFs v4.1.5 Tests from /tests/bugs/ module
                    failing on Intel
           Product: GlusterFS
           Version: 4.1
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: tests
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: chandranaik2 at gmail.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
Some of the tests from /tests/bugs module are failing on x86 on "SUSE Linux
Enterprise Server 12 SP3" in GlusterFs v4.1.5

Failing Tests from <glusterfs>/tests/bugs/ module are as mentioned below:
glusterfs-server/bug-887145.t
nfs/bug-974972.t
rpc/bug-847624.t
rpc/bug-954057.t
shard/bug-1251824.t
shard/bug-1468483.t
shard/zero-flag.t

How reproducible:
Run the tests with ./run-tests.sh or run individual tests with ./run-tests.sh
prove -vf <path to the *.t test file>

Steps to Reproduce:
1. Build GlusterFs v4.1.5
2. Run the tests as below
   ./run-tests.sh prove -vf <path to the *.t test file>

Actual results:
Tests should pass

Expected results:
Tests fail

Additional info:
Failure Details:

glusterfs-server/bug-887145.t - 
Subtest 21-24, fails with touch: cannot touch '/mnt/glusterfs/0/dir/file':
Permission denied. Whereas subtest 26 fails with error : rmdir: failed to
remove '/mnt/nfs/0/dir/*': No such file or directory

nfs/bug-974972.t
Subtest 14 fails with rm: cannot remove '/var/run/gluster/': Is a directory

rpc/bug-847624.t
Subtest 9 which does "dbench -t 10 10" fails.

rpc/bug-954057.t
Subtest 16 fails  to create the directory ‘/mnt/glusterfs/0/nobody/other’:
Permission denied

shard/bug-1251824.t, shard/bug-1468483.t
Subtest 14-26, 40-42 fails for user ‘test_user:test_user’ in the test.

shard/zero-flag.t
Sub tests fails as below:
TEST 17 (line 40): 2097152 echo
not ok 17 Got "" instead of "2097152", LINENUM:40

Please let us know if these are known failures on intel.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.