mirror of
https://github.com/zeek/zeek.git
synced 2025-10-13 03:58:20 +00:00
8049d3a002
This patch changes invocations of `spicyz` and similar Spicy tools in tests which perform compilation to use debug mode via passing `-d`. This in turn leads to Spicy compiling generated C++ code in debug as opposed to release mode which typically seems to require less CPU time and RAM. For a local test running with `btest -j 16` and no caching via `HILTI_CXX_COMPILER_LAUNCER` this sped up running of BTests under `spicy/` by about 40s on my machine (120s vs 160s).
38 lines
997 B
Text
38 lines
997 B
Text
# @TEST-REQUIRES: have-spicy
|
|
#
|
|
# @TEST-EXEC: spicyz test.spicy test.evt -d -o test.hlto
|
|
# @TEST-EXEC: zeek -NN test.hlto | grep -q ANALYZER_SPICY_TEST
|
|
# @TEST-EXEC: zeek -r ${TRACES}/http/post.trace test.zeek test.hlto "Spicy::enable_print = T;" >>output 2>&1
|
|
# @TEST-EXEC: btest-diff output
|
|
#
|
|
# @TEST-DOC: Smoke test for a custom ahead-of-time compiled Spicy analyzer hooked into Zeek.
|
|
|
|
# @TEST-START-FILE test.spicy
|
|
module test;
|
|
|
|
import zeek;
|
|
|
|
public type Dummy = unit {
|
|
# Consume all data. We split data into lines and log the number of lines and the lines when done.
|
|
data: bytes &eod &convert=$$.split(b"\r\n");
|
|
|
|
on %done { print |self.data|, self; }
|
|
};
|
|
# @TEST-END-FILE
|
|
|
|
# @TEST-START-FILE test.evt
|
|
protocol analyzer spicy::Test over TCP:
|
|
parse with test::Dummy,
|
|
port 80/tcp;
|
|
|
|
on test::Dummy -> event test::dummy(self.data);
|
|
# @TEST-END-FILE
|
|
|
|
# @TEST-START-FILE test.zeek
|
|
module test;
|
|
|
|
event test::dummy(data: vector of string)
|
|
{
|
|
print "Event:", data;
|
|
}
|
|
# @TEST-END-FILE
|