Actions
Feature #10328
closedtest valgrind leak detection by injecting intentional memory leak
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Description
- add a generic options like 'inject memory leak = true' that leaks some memory in the generic code
- create a teuthology test, probably in rados/verify, that injects the leak in teh mon and osd and verifies that valgrind detects it.
I haven't seen any memory leak failures in a while and it makes me worry the valgrind tests aren't working
Actions