Project

General

Profile

Actions
Copy link

Feature #10328

closed

test valgrind leak detection by injecting intentional memory leak

Added by Sage Weil over 9 years ago. Updated over 8 years ago.

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
Copy link
 #1

Updated by Zack Cerza over 9 years ago

  • Target version deleted (sprint20)
Actions
Copy link
 #2

Updated by Sage Weil over 8 years ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #3

Updated by Sage Weil over 8 years ago

  • Status changed from Fix Under Review to Resolved
Actions
Copy link

Also available in: Atom PDF