Drizzle

LCOV numbers showing significant drop-off

Bug #641567 reported by Patrick Crews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Patrick Crews
Drizzle 2010-10-11
7.0
Fix Released
High
Patrick Crews
Drizzle 2010-10-11

Bug Description

http://drizzle.org/lcov/

Our coverage percentages are showing a significant drop off. Previously, we were at ~70%.

No changes in code or test immediately explain this change. It is likely that the server is not shutting down properly during the coverage-gathering test run. It is known that an improperly shut down program results in a loss of the gcov coverage data - the counter files are never updated in such a case.

This is where I will start looking.

Patrick Crews (patrick-crews)
Changed in drizzle:
importance: Undecided → High
assignee: nobody → Patrick Crews (patrick-crews)
status: New → Confirmed
Revision history for this message
Patrick Crews (patrick-crews) wrote :

See http://bugs.mysql.com/bug.php?id=46327

Revision history for this message
Patrick Crews (patrick-crews) wrote :

This appears to be happening with the pbxt suite only. Every run of make test on my machines results in a forced kill of the server at the end of this suite. Kill -9 is bad for gcov counters : (

Patrick Crews (patrick-crews)
Changed in drizzle:
milestone: none → 2010-10-11
Revision history for this message
Patrick Crews (patrick-crews) wrote :

Was mistaken about the pbxt suite, however this was similar to the linked MySQL bug.

As it turns out, we were able to simply alter drizzle-automation to make use of 'make lcov' rather than the previous steps we took. The lcov report is now back to reasonable levels:
http://drizzle.org/lcov/

Please see:
https://bugs.launchpad.net/drizzle/+bug/659245
As the lcov numbers on the main index page are suspect (file and directory level reports look ok)

Revision history for this message
Patrick Crews (patrick-crews) wrote :

drizzle-automation change:
http://bazaar.launchpad.net/~drizzle-automatons/drizzle-automation/trunk/revision/205

Changed in drizzle:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.