Disable LeakSanitizer for btests that have known leaks

E.g. ones that throw interpreter exceptions,  as those are currently
known to potentially cause leaks.  Fixing the underlying leaks involves
the larger task of more IntrusivePtr usage.

Reference cycles may also cause leaks.
This commit is contained in:
Jon Siwek 2019-12-23 11:21:46 -08:00
parent d917737766
commit 0fe2a14d98
32 changed files with 100 additions and 82 deletions

View file

@ -1,7 +1,8 @@
# Expressions in an event handler that raise interpreter exceptions
# shouldn't abort Zeek entirely, but just return from the function body.
#
# @TEST-EXEC: zeek -r $TRACES/wikipedia.trace %INPUT >output
# TODO: interpreter exceptions currently may cause memory leaks, so disable leak checks
# @TEST-EXEC: ASAN_OPTIONS="detect_leaks=0" zeek -r $TRACES/wikipedia.trace %INPUT >output
# @TEST-EXEC: TEST_DIFF_CANONIFIER="$SCRIPTS/diff-remove-abspath | $SCRIPTS/diff-remove-timestamps" btest-diff reporter.log
# @TEST-EXEC: btest-diff output