[Bugs] [Bug 1672480] Bugs Test Module tests failing on s390x

bugzilla at redhat.com bugzilla at redhat.com
Wed Feb 6 11:21:34 UTC 2019


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

abhays <abhaysingh1722 at yahoo.in> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(abhaysingh1722 at ya |
                   |hoo.in)                     |



--- Comment #6 from abhays <abhaysingh1722 at yahoo.in> ---
Yes @Nithya, Below are the test cases that fail, their cause of failure and
possible workaround on Big-Endian:-

Following are the test cases which pass after changing the bricks in the test
case:-
./tests/bugs/distribute/bug-1161311.t --------passes after changing brick3 to
brick1 in subtests 31 and 41.
./tests/bugs/distribute/bug-1193636.t --------passes after changing brick3 to
brick1 in subtest 10.
./tests/bugs/nfs/bug-847622.t ----------------passes after giving absolute path
of testfile in subtest 9.

Following are the test cases that are still failing even after changing the
bricks, however if little-endian hash values are hard-coded on big-endian in
the file ./xlators/cluster/dht/src/dht-layout.c, then these test cases pass on
Big-Endian:-
./tests/bugs/glusterfs/bug-902610.t-------------subtest 7 fails
./tests/bugs/posix/bug-1619720.t----------------subtests 13 and 14 fail

Following test case is failing because of "Cannot allocate memory" issue:-
./tests/bitrot/bug-1207627-bitrot-scrub-status.t----------subtest 20 fails with
the below error:-
[client-rpc-fops_v2.c:961:client4_0_fgetxattr_cbk] 0-patchy-client-0: remote
operation failed [Cannot allocate memory]

Following test case is failing on which issue has already been raised:-
./tests/features/trash.t--------------
https://bugzilla.redhat.com/show_bug.cgi?id=1627060

So, please look into this and let us know if any workaround can be provided to
make the above tests pass on Big-Endian.

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


More information about the Bugs mailing list