Opened 11 years ago
Closed 7 years ago
#660 closed task (invalid)
Run memcheck test on Travis SI
Reported by: | mloskot | Owned by: | mloskot |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Default | Version: | main |
Severity: | Feature Request | Keywords: | travisci, buildbot |
Cc: |
Description
CMake can automatically run memory check with valgrind.
In order to run memcheck on Travis CI, currently used commands need to be updated as follows:
sudo apt-get install -qq valgrind cmake -DMEMORYCHECK_COMMAND:FILEPATH=/usr/bin/valgrind .. ctest -T memcheck
Example output:
mloskot@brzuchol:~/dev/geos/_svn/trunk/_build$ ctest -T memcheck Site: brzuchol Build name: Linux-c++ Memory check project /home/mloskot/dev/geos/_svn/trunk/_build Start 1: geos_unit 1/4 MemCheck #1: geos_unit ........................ Passed 32.56 sec Start 2: xmltester 2/4 MemCheck #2: xmltester ........................ Passed 652.60 sec Start 3: bug234 3/4 MemCheck #3: bug234 ........................... Passed 3.03 sec Start 4: TestSweepLineSpeed 4/4 MemCheck #4: TestSweepLineSpeed ............... Passed 144.27 sec 100% tests passed, 0 tests failed out of 4 Total Test time (real) = 832.47 sec Problem parsing /proc/meminfo -- Processing memory checking output: # Memory checking results: Memory Leak - 70 Potential Memory Leak - 7
The long detailed valgrind output is sent to separate file (with timestamp'ed name):
Testing/Temporary/LastDynamicAnalysis_20130828-1256.log
Let me know if the memcheck should be enabled.
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
why wouldn't we want to? I'm for it.