mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
4fbcca04e8
* Generally increase timeouts for tests that have recent transient failures * Change any test that relied on `btest-bg-wait -k` since that's never going to play with with CI systems. Instead, we always need to have a well-defined termination condition in the test itself (and most already did, so didn't really need the `-k` flag anyway).
34 lines
685 B
Text
34 lines
685 B
Text
# @TEST-EXEC: btest-bg-run zeek zeek -j -b %INPUT
|
|
# @TEST-EXEC: btest-bg-wait 30
|
|
# @TEST-EXEC: btest-diff zeek/.stdout
|
|
|
|
# So the supervised node doesn't terminate right away.
|
|
redef exit_only_after_terminate=T;
|
|
|
|
event check_status()
|
|
{
|
|
local s = Supervisor::status();
|
|
local ns = s$nodes["grault"];
|
|
|
|
if ( ! ns?$pid )
|
|
schedule 0.25sec { check_status() };
|
|
else
|
|
{
|
|
print "got supervised node status", ns$node$name;
|
|
terminate();
|
|
}
|
|
}
|
|
|
|
event zeek_init()
|
|
{
|
|
if ( Supervisor::is_supervisor() )
|
|
{
|
|
local sn = Supervisor::NodeConfig($name="grault");
|
|
local res = Supervisor::create(sn);
|
|
|
|
if ( res != "" )
|
|
print "failed to create node", res;
|
|
|
|
event check_status();
|
|
}
|
|
}
|