mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
eef7acc1e9
These have been discussed in the context of "@if &analyze" [1] and am much in favor for not disabling/removing ~100 lines (more than fits on a single terminal) out from the middle of a file. There's no performance impact for having these handlers enabled unconditionally. Also, any future work on "@if &analyze" will look at them again which we could also skip. This also reverts back to the behavior where the Cluster::LOG stream is created even in non cluster setups like in previous Zeek versions. As long as no one writes to it there's essentially no difference. If someone does write to Cluster::LOG, I'd argue not black holing these messages is better. Schema generators using Log::active_streams will continue to discover Cluster::LOG even if they run in non-cluster mode. https://github.com/zeek/zeek/pull/3062#discussion_r1200498905 |
||
|---|---|---|
| .. | ||
| benchmark/broker | ||
| btest | ||
| builtin-plugins | ||
| coverage | ||
| external | ||
| scripts | ||
| .gitignore | ||
| CMakeLists.txt | ||
| Makefile | ||
| README | ||
This directory contains suites for testing for Zeek's correct
operation:
btest/
An ever-growing set of small unit tests testing Zeek's
functionality.
external/
A framework for downloading additional test sets that run more
complex Zeek configuration on larger traces files. Due to their
size, these are not included directly. See the README for more
information.
scripts/
Helpers scripts used by some tests.