mirror of
https://github.com/zeek/zeek.git
synced 2025-10-06 08:38:20 +00:00
e6f4e01041
Or otherwise convert into a regular btest if it didn't already seem to be covered. There's no need for a separate memory leak test group since compiling with LeakSanitizer now covers leak checking for the full btest suite.
10 lines
293 B
Text
10 lines
293 B
Text
# @TEST-EXEC: zeek -r $TRACES/wikipedia.trace %INPUT
|
|
|
|
@load policy/misc/stats
|
|
|
|
event load_sample(samples: load_sample_info, CPU: interval, dmem: int)
|
|
{
|
|
# This output not part of baseline as it varies, but guess this test
|
|
# should still exist to cover potential memory leaks.
|
|
print CPU;
|
|
}
|