mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38: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).
46 lines
1.1 KiB
Text
46 lines
1.1 KiB
Text
# @TEST-REQUIRES: have-spicy
|
|
#
|
|
# @TEST-EXEC: spicyz -d -o test.hlto text.spicy ./text.evt
|
|
# @TEST-EXEC: zeek -r ${TRACES}/http/post.trace test.hlto %INPUT >output
|
|
# @TEST-EXEC: btest-diff output
|
|
# @TEST-EXEC: btest-diff weird.log
|
|
|
|
event zeek_init()
|
|
{
|
|
# Check we can access the tag.
|
|
print Files::ANALYZER_SPICY_TEXT;
|
|
}
|
|
|
|
event text::data(f: fa_file, data: string)
|
|
{
|
|
print "text data", f$id, data;
|
|
}
|
|
|
|
# @TEST-START-FILE text.spicy
|
|
module Text;
|
|
|
|
import zeek;
|
|
|
|
public type Data = unit {
|
|
data: bytes &eod;
|
|
|
|
on %done {
|
|
# File ID isn't stable across platforms, so just check expected length.
|
|
assert |zeek::fuid()| == 18;
|
|
zeek::weird("test_weird");
|
|
}
|
|
};
|
|
# @TEST-END-FILE
|
|
|
|
# @TEST-START-FILE text.evt
|
|
|
|
file analyzer spicy::Text:
|
|
parse with Text::Data,
|
|
|
|
# Note that Zeek determines the MIME type not from the Content-Type
|
|
# header in the trace, but by content sniffing (i.e., libmagic-style)
|
|
mime-type text/plain;
|
|
#mime-type application/x-www-form-urlencoded;
|
|
|
|
on Text::Data -> event text::data($file, self.data);
|
|
# @TEST-END-FILE
|