Key: |
QB-1269
|
Type: |
Bug
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
U. Artie Eoff
|
Votes: |
0
|
Watchers: |
1
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 16/May/12 04:52 AM
Updated: 26/May/12 12:21 AM
|
|
Component/s: |
None
|
Affects Version/s: |
4.0.31
|
Fix Version/s: |
4.0.40
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Fedora 16 x86_64 (Linux)
|
|
Boost.Test reports the TestingTime as microseconds (e.g. 20000 microseconds = 0.02 seconds). However, the QuickBuild Boost Test Reporter plugin interprets the TestingTime value as milliseconds. That is, the Boost Test Reporter plugin displays 20s in the QuickBuild report when boost.test results reports 20000 (which is in microseconds).
If you examine the boost.test source code, you'll find that it uses a boost.timer to measure the test time. boost::timer.elapsed() returns its result as seconds (double). Finally, boost.test then logs "timer.elapsed() * 1e6" to the boost.test report (i.e. in microseconds).
|
Description
|
Boost.Test reports the TestingTime as microseconds (e.g. 20000 microseconds = 0.02 seconds). However, the QuickBuild Boost Test Reporter plugin interprets the TestingTime value as milliseconds. That is, the Boost Test Reporter plugin displays 20s in the QuickBuild report when boost.test results reports 20000 (which is in microseconds).
If you examine the boost.test source code, you'll find that it uses a boost.timer to measure the test time. boost::timer.elapsed() returns its result as seconds (double). Finally, boost.test then logs "timer.elapsed() * 1e6" to the boost.test report (i.e. in microseconds). |
Show » |
There are no comments yet on this issue.
|
|