You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Rene Cannao bee37b2cb8 fix(tester): abort when TAP_GROUP is set but has no tests registered ... 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.		1 month ago
..
bin	fix(tester): abort when TAP_GROUP is set but has no tests registered	1 month ago
datadir	…
deps	…
etc	Remove jenkins-build-scripts dependencies from test scripts	2 months ago
lib	…
patches	…
Makefile	…
proxysql_cluster_init.sh	…
proxysql_start.sh	…
proxysql_stop.sh	…