4paradigm / 4paradigm/OpenMLDB
ut: so many unit test have memory leak, we should use sanitizer to check
Open
bug
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
This issue has no description.
Contributor guide
Research direction
The issue mentions using a sanitizer to check for memory leaks in unit tests. First, identify which unit tests are referenced and the build system used. Research how to integrate a memory sanitizer like AddressSanitizer into the existing test suite. Determine the steps to run the sanitizer and interpret its output to locate leaks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100