Bug #1588

Failing test in timesync sub-project

Added by J. Moringen over 9 years ago. Updated over 9 years ago.

Status:ResolvedStart date:08/07/2013
Priority:NormalDue date:
Assignee:J. Wienke% Done:

100%

Category:Timesync
Target version:rsb-0.10

Description

For maybe 1 out of 3 executions of the test suite, I see this failure:

$ ctest --output-on-failure
Test project /homes/jmoringe/code/cor-lab/rsb/rsb-tools-cpp/build-x86_64
    Start 1: rsbtimesynctest
1/1 Test #1: rsbtimesynctest ..................***Failed    1.68 sec
[==========] Running 3 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 3 tests from ApproximateTimeStrategyTest
[ RUN      ] ApproximateTimeStrategyTest.testEqualFrequencyAndTiming
[       OK ] ApproximateTimeStrategyTest.testEqualFrequencyAndTiming (402 ms)
[ RUN      ] ApproximateTimeStrategyTest.testOneDoubleFrequency
/homes/jmoringe/code/cor-lab/rsb/rsb-tools-cpp/test/timesync/rsb/tools/timesync/ApproximateTimeStrategyTest.cpp:196: Failure
Value of: actual
  Actual: "7" 
Expected: expected
Which is: "6" 
[  FAILED  ] ApproximateTimeStrategyTest.testOneDoubleFrequency (953 ms)
[...]

Associated revisions

Revision 7634a630
Added by J. Wienke over 9 years ago

fixes #1588: use virtual time for unit tests

Prevent timing issues by using a virtual time for unit tests.

History

#1 Updated by J. Wienke over 9 years ago

  • Status changed from New to In Progress

#2 Updated by J. Wienke over 9 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset rsb-tools-cpp|commit:7634a630ab53eab3db6a62d8d9ecc3ab894a92cd.

Also available in: Atom PDF