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 8c2275178a test: fail proxysql-tester.py TAP runs when zero binaries are discovered ... Defence-in-depth against the silent false-green failure mode we just tracked down. Previously, if CI-builds produced no TAP test binaries on the host (for any reason -- wrong make target, broken volume mount, typo in a docker-compose override, misconfigured groups.json), the tester would walk three workdirs, find zero `*-t` binaries in each, report: SUMMARY: 'tests' PASS 0/0 : FAIL 0/0 : SKIP 0/0 SUMMARY: 'deprecate_eof_support' PASS 0/0 : FAIL 0/0 : SKIP 0/0 SUMMARY: 'unit' PASS 0/0 : FAIL 0/0 : SKIP 0/0 SUMMARY: ret_rc = [0] ...and exit 0. Zero failures out of zero tests is technically "success" by the old logic, so the workflow would turn green. Combined with a build-target regression on the GH-Actions branch, this masked the fact that the entire TAP test suite (CI-legacy-g*, CI-mysql84-g*, CI-basictests, CI-taptests-pgsql-cluster, CI-legacy-clickhouse-g1, CI-legacy-g2-genai) had been running zero tests per commit for several weeks while still reporting green. Safety net ---------- At the end of `run_tap_tests`, check whether `glob(*-t)` found ANY binaries across ALL workdirs. The summary tuple (cmd, rc) is populated for every discovered binary, including ones that end up skipped by version filter or INCL/EXCL regexes -- those get `rc=None` rather than being absent. So `len(ret_summary) == 0` is a strict "nothing was even on disk" signal. When that happens, check groups.json for how many tests TAP_GROUP is expected to run. If N > 0, log a SAFETY NET FAIL line and bump ret_rc to 1. Version-filter skips and INCL/EXCL skips are not affected -- they still produce summary entries, so ret_summary is non-empty in those cases. Only the actual "test binaries were never built" case trips the guard. If TAP_GROUP is unset (running the full TAP suite), any zero-discovery result is a failure regardless -- there's no legitimate configuration where proxysql-tester should run zero tests. This complements the ci-builds.yml fix on the GH-Actions branch that restores the TAP build target. With both in place, a future regression in either the build or the test discovery chain surfaces loudly instead of silently.		2 months ago
..
Pipfile	security: fix all 48 Dependabot alerts — bump Python test deps	2 months ago
proxysql-tester.py	test: fail proxysql-tester.py TAP runs when zero binaries are discovered	2 months ago
requirements-ubuntu24.txt	security: fix all 48 Dependabot alerts — bump Python test deps	2 months ago
requirements.txt	security: fix all 48 Dependabot alerts — bump Python test deps	2 months ago