summaryrefslogtreecommitdiff
path: root/libs/pbd/test
diff options
context:
space:
mode:
authorTim Mayberry <mojofunk@gmail.com>2015-09-14 11:19:17 +1000
committerTim Mayberry <mojofunk@gmail.com>2015-09-16 11:22:16 +1000
commitf4cb4e479da988df8f8d0dcb369e0ba4b358128e (patch)
treee4442f89e29a36fb2ac7650ead054231297d256f /libs/pbd/test
parentcd05d46c007583a27be23e2ae8cedc5ea9746373 (diff)
Rename PBD::QPC::get_timer_valid to check_timer_valid and perform timer test
I'm not sure if this test is going to be effective as I don't have hardware to test on at the moment. As noted in the documentation, Windows XP should be the only OS where QPC uses a timer source that is non-monotonic(multi-core with non-syncronized TSC).
Diffstat (limited to 'libs/pbd/test')
-rw-r--r--libs/pbd/test/windows_timer_utils_test.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/libs/pbd/test/windows_timer_utils_test.cc b/libs/pbd/test/windows_timer_utils_test.cc
index fe5e1a24df..1566f37d96 100644
--- a/libs/pbd/test/windows_timer_utils_test.cc
+++ b/libs/pbd/test/windows_timer_utils_test.cc
@@ -13,7 +13,8 @@ CPPUNIT_TEST_SUITE_REGISTRATION (WindowsTimerUtilsTest);
void
WindowsTimerUtilsTest::testQPC ()
{
- CPPUNIT_ASSERT (PBD::QPC::get_timer_valid());
+ // performs basically the same test
+ CPPUNIT_ASSERT (PBD::QPC::check_timer_valid());
int64_t last_timer_val = PBD::QPC::get_microseconds ();
CPPUNIT_ASSERT (last_timer_val >= 0);