[Gluster-infra] [Bug 1758139] New: Modify logging at Gluster regression tests

2019-10-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1758139 Bug ID: 1758139 Summary: Modify logging at Gluster regression tests Product: GlusterFS Version: 7 Status: NEW Component: project-infrastructure Assignee:

[Gluster-infra] [Bug 1757804] Code coverage - call frequency is wrong

2019-10-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1757804 --- Comment #4 from M. Scherer --- so maybe the problem is that since the code is using spinlock sometime (but not always), and spinlock by nature would be a empty loop, then it might explain for that specific case why it do run more often

[Gluster-infra] [Bug 1757804] Code coverage - call frequency is wrong

2019-10-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1757804 --- Comment #3 from M. Scherer --- We are using the RHEL 7 version (gcov), so yeah, that's indeed old. We could switch to Fedora builders, but that would imply that the test suite is running on Fedora and compile on it, even with a newer GCC

[Gluster-infra] [Bug 1757804] Code coverage - call frequency is wrong

2019-10-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1757804 --- Comment #2 from Yaniv Kaul --- Amar was under the impression we are running an old version of whatever is measuring the coverage. Could it be? -- You are receiving this mail because: You are on the CC list for the bug.

[Gluster-infra] [Bug 1757804] Code coverage - call frequency is wrong

2019-10-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1757804 M. Scherer changed: What|Removed |Added CC||msche...@redhat.com --- Comment #1 from