MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015160CMakeCTestpublic2014-09-16 12:032016-06-10 14:31
Reportertrsystran 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.12.2 
Target VersionFixed in Version 
Summary0015160: Different timeout for test and memcheck
DescriptionCurrently memcheck uses the same timeout (global or test-local) as for normal ctest_test() run.

This is an issue since valgrind has a slowdown factor between 5 to 100 (according to them): the normal timeouts are not relevant for memcheck runs.


Possible solutions with existing code:
1/ always calibrate the test timeout for valgrind. Drawback: this value is too large for normal test runs.
2/ never use test-local timeout and only rely on global timeout: then change the CTEST_TEST_TIMEOUT before calling ctest_memcheck(). Drawback: test-local timeout are really useful so stopping using them is an issue.


Possible solutions with patches:
Create a new test property MEMCHECK_TIMEOUT, a new global default memcheck timeout, that only apply for memcheck runs.
Default value: either their non memcheck counterpart; or use a global slowdown factor and apply it from non memcheck timeout values.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-09-16 12:03trsystranNew Issue
2016-06-10 14:29Kitware RobotNote Added: 0042632
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0042632)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.