<div dir="ltr">Hi Abhay,<div><br></div><div>Would it be possible for you to change the namsepace.t and trash.t (as discussed in IRC) tests to work with both endian architectures?</div><div><br></div><div>Both failures seem to be linked to the issue that SuperFastHash() provides different values on little & big endian architectures. You could do something like `lspcu | grep "Little Endian" to determine the endianess and this value can be used to have the right behavior in tests.</div><div><br></div><div>Please feel free to let me know if you need more assistance in fixing both namespace.t and trash.t tests.</div><div><br></div><div>Regards,</div><div>Vijay</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 13, 2018 at 12:26 PM Abhay Singh <<a href="mailto:abhays@us.ibm.com">abhays@us.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">Hi,</font><br><font size="2" face="sans-serif">I am working on Glusterfs v4.1.1 for
Ubuntu 16.04 on big endian architecture. After successful build and running
the test cases, I encountered a test case failure. The test case is:-</font><br><font size="2" face="Symbol">· </font><font size="2" face="sans-serif">./tests/basic/namespace.t</font><br><br><font size="2" face="sans-serif">In the test case <b>./tests/basic/namespace.t</b>,
a NAMESPACE_HASH is generated after calling a SuperFastHash()
function on the corresponding folder names. This hash differs on big endian
and little endian architectures. Therefore, I have changed the code
accordingly. Although there is another subtest in this test which fails
with the following error:-</font><br><font size="2" face="sans-serif">TEST 30 (line 119): Y check_samples
CREATE 1268089390 /namespace3/file patchy0</font><br><font size="2" face="sans-serif">getfattr: /d/backends/patchy0/namespace3/file:
No such file or directory</font><br><br><font size="2" face="sans-serif">As seen above, the error is occurring
because the folder /d/backends/patchy0/namespace3/ doesn’t contain “file”.
However, I resolved this subtest by changing the folder to /d/backends/patchy6/namespace3/
where “file” is actually present. </font><br><font size="2" face="sans-serif">But same is not the case for little
endian architectures where the test case passes without any changes. </font><br><font size="2" face="sans-serif">The type of filesystem /d/backends is
“ext4” and there is enough space allocated to the directory.</font><br><font size="2" face="sans-serif">Therefore, could you please provide
me with some more insight as to why is this happening?</font><br><br><br><font size="1" color="#004080" face="sans-serif"><b>Thanks and Regards,</b></font><br><font size="1" color="#004080" face="sans-serif"><b>Abhay Singh</b></font><br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div>