Description of problem:
Check https://build.gluster.org/job/line-coverage/226/Line_Coverage_Report/ and check xlators/features/sdfs/ coverage. It is 0 even though the translator is now being executed sdfs-sanity.t
Version-Release number of selected component (if applicable):
The line coverage should capture all these executions.
REVIEW: https://review.gluster.org/19629 (tests: don't kill the process directly with KILL signal) posted (#1) for review on master by Amar Tumballi
COMMIT: https://review.gluster.org/19629 committed in master by "Xavi Hernandez" <firstname.lastname@example.org> with a commit message- tests: don't kill the process directly with KILL signal
Instead send the SIGTERM (default, 15) first, and at the end
send SIGKILL. If SIGKILL is sent directly, we miss many tests
like valgrind, lcov etc., not able to process the information
Signed-off-by: Amar Tumballi <email@example.com>
Latest master is all fine. As this doesn't need a specific release, closing the issue.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.
glusterfs-v4.1.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.