routing/naywatch/test-version.sh, branch masterMirror of routing feedhttps://git.openwrt.org/feed/routing/atom?h=master2026-08-10T07:43:05Znaywatch: correct the reason recorded in test-version.sh2026-08-10T07:43:05ZJosef Schlehofer2026-08-06T12:13:40Zurn:sha1:2fe4311dbc0f4046285ed22155e221f56c5e4f51
The comment claimed the version check has to be skipped because
running the script may trigger a reboot. That is not what happens:
reboot_now() is only reached once naywatch has seen a neighbour
(ACTIVE=1) and then lost it for more than MIN_KICK intervals, and
the watchdog branch is not taken either, because the probe leaves
use_watchdog empty.
What does happen is that naywatch takes positional arguments - check
interval, watchdog timeout, and so on - rather than options, so a
probe flag ends up as the check interval and the script enters its
monitoring loop instead of reporting anything, until the probe
timeout kills it.
The override stays, only its justification is corrected.
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
naywatch: add test-version.sh for CI runtime tests2026-08-10T07:43:05ZJosef Schlehofer2026-08-06T07:47:33Zurn:sha1:361d14cb3f6c4ce520d230c0116055bc583adabd
naywatch is a watchdog shell script which does not provide any
option to report its version, so the generic version check of the CI
runtime tests fails for this package. On top of that, the generic
check executes each installed executable with several flags to probe
for the version, which must never happen for a watchdog script that
may trigger a reboot of the test environment.
Providing a test-version.sh both skips the version probing of the
binary and overrides the version check.
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>