[Bugs] [Bug 1508025] New: symbol-check.sh is not failing for legitimate reasons

[bugzilla at redhat.com]

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

            Bug ID: 1508025
           Summary: symbol-check.sh is not failing for legitimate reasons
           Product: GlusterFS
           Version: mainline
         Component: tests
          Assignee: kkeithle at redhat.com
          Reporter: srangana at redhat.com
                CC: bugs at gluster.org, ndevos at redhat.com, nigelb at redhat.com



Description of problem:

On investigation of this
(http://lists.gluster.org/pipermail/gluster-devel/2017-October/053861.html)
mail thread in devel, it is seen that for 3.10 branch symbol-check.sh should
always report a failure, but does not do so.

On master the reason for failure is addressed via the commit: 
https://review.gluster.org/#/c/16820/

But, the commit also reads that the problem was identified on a local run and
not due to failures in the regression setup.

So, on further investigation of why symbol check is not reporting failures, I
found that on my local Fedora26 machine, the test actually fails on the 3.10
branch.

On checking with Nigel, to look into the regression machines, he has noted that
it passes there as the script is not catching the symbol.

I will let Nigel post his observations.

The issue seems to stem from the fact that the 'nm' list of symbols in the
regression machines spews out a lstat64 and not a __lxstat64 that the script is
looking for. This needs correction.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bYNJhVIb41&a=cc_unsubscribe