mirror of
https://github.com/zeek/zeek.git
synced 2025-10-08 01:28:20 +00:00
![]() The script added as a test case reports the following messages *and* dumps a core file. Printing the first error and a normal failure exit seems sufficient. IMO triggering an abort() due to user scripting issues is not something that Zeek should do $ zeek ./identifier-not-defined-error.zeek error in ./identifier-not-defined-error.zeek, line 10: identifier not defined: MyEnu error in ./identifier-not-defined-error.zeek, line 10 and error: &default value has inconsistent type (M::MY_ENUM_A and error) internal error in ./identifier-not-defined-error.zeek, line 11: type inconsistency in ZVal constructor Aborted (core dumped) Change is to skip certain checks when an error type is propagated. |
||
---|---|---|
.. | ||
benchmark/broker | ||
btest | ||
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.