Smoke Test

CPU test incorrectly reports time taken for test

Bug #362759 reported by Jonathan Rothwell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Smoke Test
Confirmed
High
Jonathan Rothwell
Smoke Test 1.0-beta

Bug Description

This appears to be something to do with clock_ticks_per_second, and it also affects the results of this test.

Related branches

lp:smoketest/trunk
Revision history for this message
Jonathan Rothwell (jrothwell97) wrote :

Assigned to me - I coded it, it's my problem.

Changed in smoketest:
assignee: nobody → jrothwell97
importance: Undecided → High
milestone: none → 1.0-beta
status: New → Confirmed
Revision history for this message
Jonathan Rothwell (jrothwell97) wrote :

Just for general information: this bug is here because Smoke Test is wildly inaccurate in reporting the time the CPU test took. For example, in a test that took 4.24 seconds using an independent stopwatch, it reported the time taken as being 0.11 seconds.

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.