summaryrefslogtreecommitdiff
path: root/vcl/Module_vcl.mk
diff options
context:
space:
mode:
authorAshod Nakashian <ashodnakashian@yahoo.com>2015-08-20 21:06:06 -0400
committerThorsten Behrens <Thorsten.Behrens@CIB.de>2015-08-23 21:19:20 +0000
commitb103e7d786f5b7ec6cfe4f53f2ca317f06ceabc5 (patch)
tree88b07d43a7ea73bd47cf74529ca6190011f7778e /vcl/Module_vcl.mk
parenta401cf33b2e05d1778faef8e4fdd1043d3eb9b2e (diff)
vcl: unittests for Timer and AutoTimer.
Enabled VCL Timer unittests on Windows builds and added two unittests to detect misfiring of timer events. Due to the nature of timer events having virtually no guarantees on non-realtime operating systems, the tests may fail randomly under different system loads. The tests repeat a few times in such cases, but still there are no guarantees. These tests are added to detect gross breaks in the timer algorithms and to improve certain corner cases. They are designed to minimize any random failures. Posterity might hate me for committing such unittests, so I added TEST_TIMERPRECISION directive to include/exclude the tests at compile time. It should be enabled if it causes more harm than good. Change-Id: If2856f194cb4732c84900113bdb969f397f67d5a Reviewed-on: https://gerrit.libreoffice.org/17906 Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de> Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Diffstat (limited to 'vcl/Module_vcl.mk')
-rw-r--r--vcl/Module_vcl.mk7
1 files changed, 7 insertions, 0 deletions
diff --git a/vcl/Module_vcl.mk b/vcl/Module_vcl.mk
index c3e84e613521..c949f4275580 100644
--- a/vcl/Module_vcl.mk
+++ b/vcl/Module_vcl.mk
@@ -123,4 +123,11 @@ $(eval $(call gb_Module_add_check_targets,vcl,\
CppunitTest_vcl_timer \
))
endif
+
+# Is any configuration missing?
+ifeq ($(OS),WNT)
+$(eval $(call gb_Module_add_check_targets,vcl,\
+ CppunitTest_vcl_timer \
+))
+endif
# vim: set noet sw=4 ts=4: