Opened 7 years ago
Last modified 6 years ago
#1567 closed defect
valgrind for system tests — at Version 2
| Reported by: | Dimitar Misev | Owned by: | dkamov |
|---|---|---|---|
| Priority: | major | Milestone: | 9.7 |
| Component: | systemtest | Version: | development |
| Keywords: | memleak, test, valgrind | Cc: | Dimitar Misev, Vlad Merticariu, Peter Baumann |
| Complexity: | Hard |
Description (last modified by )
Add a systemtest/testcases_mandatory/test_memory_leaks/test.sh script that will run same as test_select, but use the following instead of rasql:
valgrind --tool=memcheck --leak-check=full --track-origins=yes directql ..
In the output/ directory the output of valgrind should be saved (not the query result like in test_select). The goal of the test is to look in this output from valgrind and determine if there is excessive memory leak. The oracle/ directory could contain the amount of maximum acceptable leaked bytes for each query.
Afterwards (in separate tickets) we can work to fix any memory leaks, and reduce the acceptable amounts in the oracle directory.
Change History (2)
comment:1 by , 7 years ago
| Cc: | added |
|---|
comment:2 by , 6 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | 10.0 → 9.7 |
| Owner: | set to |
| Reporter: | changed from to |
| Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.
