MantisBT - CMake | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0015159 | CMake | CTest | public | 2014-09-16 10:47 | 2016-06-10 14:31 |
Reporter | trsystran | ||||
Assigned To | Kitware Robot | ||||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | moved | ||
Platform | OS | OS Version | |||
Product Version | CMake 2.8.10.1 | ||||
Target Version | Fixed in Version | ||||
Summary | 0015159: MemCheck & CDash: timeout reported as "failed" instead of "timeout" | ||||
Description | When running a MemCheck in CTest, some tests fail because of timeout limits. In such case the information is available in the ctest stdout/err: 240/1445 MemCheck 0000146: some_test ....................................***Timeout 65.92 sec But it is not reported in the DynamicAnalysis.xml sent to CDash: <Test Status="failed"> <Name>some_test/Name> <Path>xxx/Path> <FullName>some_test</FullName> <FullCommandLine>/usr/bin/valgrind xxx</FullCommandLine> <Results> </Results> <Log>blah</Log> </Test> This information would be useful in CDash, like it's already done for normal tests. In CDash we only get "failed" status and we don't know why it has failed. | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2014-09-16 10:47 | trsystran | New Issue | |||
2016-06-10 14:29 | Kitware Robot | Note Added: 0042631 | |||
2016-06-10 14:29 | Kitware Robot | Status | new => resolved | ||
2016-06-10 14:29 | Kitware Robot | Resolution | open => moved | ||
2016-06-10 14:29 | Kitware Robot | Assigned To | => Kitware Robot | ||
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Notes | |||||
|
|||||
|
|