[cmake-developers] [CMake 0015160]: Different timeout for test and memcheck
Mantis Bug Tracker
mantis at public.kitware.com
Tue Sep 16 12:03:05 EDT 2014
The following issue has been SUBMITTED.
======================================================================
http://www.cmake.org/Bug/view.php?id=15160
======================================================================
Reported By: trsystran
Assigned To:
======================================================================
Project: CMake
Issue ID: 15160
Category: CTest
Reproducibility: N/A
Severity: feature
Priority: normal
Status: new
======================================================================
Date Submitted: 2014-09-16 12:03 EDT
Last Modified: 2014-09-16 12:03 EDT
======================================================================
Summary: Different timeout for test and memcheck
Description:
Currently 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2014-09-16 12:03 trsystran New Issue
======================================================================
More information about the cmake-developers
mailing list