[Gluster-infra] [Bug 1757804] New: Code coverage - call frequency is wrong
bugzilla at redhat.com
bugzilla at redhat.com
Wed Oct 2 13:27:34 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1757804
Bug ID: 1757804
Summary: Code coverage - call frequency is wrong
Product: GlusterFS
Version: mainline
Status: NEW
Component: project-infrastructure
Severity: medium
Assignee: bugs at gluster.org
Reporter: ykaul at redhat.com
CC: bugs at gluster.org, gluster-infra at gluster.org
Target Milestone: ---
Classification: Community
We might be using an old release of the tool, but currently, it has issues with
the call frequency. As an example:
From
https://build.gluster.org/job/line-coverage/Line_20Coverage_20Report/libglusterfs/src/fd-lk.c.gcov.html:
1051783 : fd_lk_ctx_unref(fd_lk_ctx_t *lk_ctx)
64 : {
65 1051783 : int ref = -1;
66 :
67 1051783 : GF_VALIDATE_OR_GOTO("fd-lk", lk_ctx, err);
68 :
69 1051783 : ref = GF_ATOMIC_DEC(lk_ctx->ref);
70 1051783 : if (ref < 0)
71 0 : GF_ASSERT(!ref);
72 1051783 : if (ref == 0)
73 738446 : _fd_lk_destroy_lock_list(lk_ctx);
74 :
75 1051798 : if (ref == 0) {
76 738443 : LOCK_DESTROY(&lk_ctx->lock);
77 738442 : GF_FREE(lk_ctx);
How exactly is line 75 called more than the others, and the whole function?!
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Gluster-infra
mailing list