mirror of https://github.com/sysown/proxysql
Previously, if TAP_GROUP was set but the group had no entries in
test/tap/groups/groups.json (typo, missing registration, etc.), the
tester logged a warning and silently fell back to running ALL 325 TAP
tests. In a multi-group parallel run this turns a misconfiguration into
a multi-hour hang that only surfaces when the per-group TIMEOUT fires.
We hit this in practice: mysql90-g[2-5] existed as launch targets in
the runner but hadn't been populated in groups.json yet. The tester
fell back to the full suite, and the groups TIMED OUT after chewing
through pgsql tests they had no business running.
Change behavior to log at CRITICAL and sys.exit(1) in two cases:
1. TAP_GROUP is set, groups.json is present, but the group has no
tests registered.
2. TAP_GROUP is set and groups.json is missing entirely.
The "no TAP_GROUP specified" path is unchanged — that's the legitimate
way to run the full suite directly (outside the group runner).
Error messages explicitly tell the operator what to do: either register
tests for the group, or unset TAP_GROUP to run the full suite
intentionally.
v3.0-dbdeployer-mysql84-gr
parent
7eee687415
commit
bee37b2cb8
Loading…
Reference in new issue