You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of memory leak sanitized program exit with non zero exit code. But we do not care for the exit code for core = tarantool tests. As a result test will pass. In order to test for memory leaks we should fail in this case.
Or may be we should fail if there is ERROR: LeakSanitizer: detected memory leaks in stderr output of the program.
Currently we stop default server in worker run loop only before the
next test start. So the previous test does not account whether the
Tarantool executing the test exits successfully or not. Thus we
do not fail on memory leaks for example.
Let's stop the server and account its exit status in test.
Closestarantool#416
nshy
linked a pull request
Jul 16, 2024
that will
close
this issue
In case of memory leak sanitized program exit with non zero exit code. But we do not care for the exit code for
core = tarantool
tests. As a result test will pass. In order to test for memory leaks we should fail in this case.Or may be we should fail if there is
ERROR: LeakSanitizer: detected memory leaks
in stderr output of the program.Changes for demo:
Test for leak detection on simple run:
Test for leak detection for
core = tarantool
test:There is similar issue for luatest tarantool/luatest#349.
The text was updated successfully, but these errors were encountered: