Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests: unit test to cause a problem in kmemleak #2229

Open
RomanBelozerov opened this issue Aug 30, 2024 · 0 comments
Open

tests: unit test to cause a problem in kmemleak #2229

RomanBelozerov opened this issue Aug 30, 2024 · 0 comments

Comments

@RomanBelozerov
Copy link
Contributor

We have the issue about the adding a new CI job for kernel with sanitizers and checkers. (See #23 and #2211). We have implemented memory check using lmemleak for each test from tempesta-test (-m option) and we have job for this. But this check may be unreliable because there is no warranty that test framework expects the result. (it can work differently for different VMs).

So we need a function or unit tests in TempestaFW that will 100% cause problem and we will be able to find it in python tests using kmemleak (-m option)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants