tarantool / tarantool/tarantool
Run tests under valgrind in CI
Open
Nobody has claimed this yet.
qa
raw idea
- Dominant language
- Lua
- Stars
- 3.7k
- Forks
- 419
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 88
Description
Run tests under valgrind in CI.
Are we need to disable the lookaside memory allocator.
(imported from google doc)
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 locating the repository's CI configuration and existing test command. Determine how Valgrind should run there and whether the lookaside memory allocator must be disabled; done means CI executes the tests under Valgrind with the allocator setting decided and the checks pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100