PointCloudLibrary / PointCloudLibrary/pcl
Running unit tests with valgrind on CI
Open
Nobody has claimed this yet.
kind: proposal
module: ci
status: stale
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 4.7k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 6
Description
How do everyone here think about running unit tests with valgrind on CI to check for potential memory problems? The trade off is longer run time on CI but I don't think a fast run time on CI is necessary.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's CI configuration and existing unit-test jobs. Determine how Valgrind could be incorporated, what runtime trade-offs are acceptable, and which memory-checking results would count as done; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100