proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	4e4d4496aa	ci(cache): pre-compress _test/_bin caches with zstd --ultra -22 `actions/cache@v4` ships its payload through zstd at level ~3. The _test and _bin caches saved by CI-builds and consumed by every downstream TAP/3p workflow add up to several GB each and routinely push the repo past GitHub's 10 GB per-repo cache quota. The LRU eviction that follows deletes caches between save and restore, breaking the entire TAP pipeline with cryptic "Cache restore test" failures. Wrap both caches so they travel as `cache_<kind>.tar.zst`: - In CI-builds: add a "Pack <kind> cache with zstd-22" step that does `tar -cf - <paths> \| zstd --ultra -22 -T0 -o ../cache_<kind>.tar.zst` before the `actions/cache/save@v4` step. The save now uploads a single .tar.zst blob; the action's level-3 re-compression on already-maximally-compressed data is a near no-op. - In every consumer workflow (55 files): change the restore `path:` to the single-line scalar `cache_<kind>.tar.zst` and add an "Unpack <kind> cache" step right after that does `zstd -d < ../cache_<kind>.tar.zst \| tar -xf -` from inside `proxysql/`, recreating the original layout (`proxysql/test/`, `proxysql/.git/`, `proxysql/binaries/`). Footprint reduction is ~25-30% on the wire, which is enough headroom to keep two concurrent cascades under the 10 GB quota. Compatibility note: the cache version embeds the path list, so this change invalidates the existing _test/_bin caches. The first run on a given SHA after this lands has to rebuild; subsequent runs hit the new compressed cache normally. Old caches age out via LRU. The cache key format itself (including all `_test` / `_bin` / `_src` / `_matrix` suffixes and per-shard `inputs.trigger`/`github.sha` expressions) is preserved verbatim. Scope: only `_test` and `_bin` caches are touched. `_src`, `_matrix`, `_3p-*`, codeql, and other caches are left alone.	1 month ago
Rene Cannao	08a19245b5	Fix summary log glob: match subdirectory layout ./logs/${NOW}/_summary.log fn_summary in common.bash writes to ./logs/${NOW}/${SUITE}_summary.log (e.g. ./logs/20260325-002217/aiomysql_summary.log) but Check baseline was looking for ./logs/_summary.log — and shell glob * doesn't cross directory boundaries. Changed to ./logs//_summary.log to match the actual file location in the ${NOW} timestamped subdirectory.	3 months ago
Rene Cannao	fdd87c677a	Fix false-green CI in all 3p test workflows The "Check baseline" step in all 10 ci-3p-*.yml workflows could report success even when tests completely failed or never ran, because: 1. Missing summary log → FAILS variable empty → exit ${FAILS:-0} → exit 0 2. pytest ERROR counts (fixture/setup failures) were ignored, only FAIL counts were checked — so tests that all error at setup showed as green 3. Unparseable summary log format → same empty FAILS → false success 4. "Check baseline" had no if: condition, so it was skipped when "Run tests" failed, letting run-tests.bash's exit code (often 0) stand 5. Artifacts were only uploaded on failure(), but failure was never detected, destroying debug evidence Fixes applied to all 10 workflows: - Add if: !cancelled() to "Check baseline" so it always evaluates results - Fail explicitly when summary log is missing - Fail explicitly when FAIL count cannot be parsed - Parse and fail on ERROR count (setup/fixture failures) - Change artifact upload from failure() to !cancelled() for always-on logs - Fix inconsistent artifact naming (missing dash before 'logs')	3 months ago
Miro Stauder	bb7267922b	update docker-hoster image	5 months ago
Miro Stauder	1ec0c3e201	use updated docker-hoster	5 months ago
Miro Stauder	f2b39f11a3	always use debug build for 3p tests	10 months ago
Miro Stauder	b9bd27c575	do not fail if baseline missing	10 months ago
Miro Stauder	53a79bce9d	update triggers	10 months ago

8 Commits (ci-pgsql-socket-g1)