proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	e59e55b0a3	ci(coverage): extend Codecov TAP upload to all remaining TAP groups Fan-out of PR #5818's two-line pattern to every TAP-group reusable workflow that wasn't yet contributing to Codecov: legacy-clickhouse-g1, legacy-g1, legacy-g3..g9, mariadb10-galera-g1..g9, mysql56-single-g1, mysql84-g1..g9, mysql84-gr-g1..g9, set_parser_algorithm_3-g1 (38 reusables total) For each ci-<group>.yml on GH-Actions: - permissions: write-all (id-token:write for codecov OIDC) - BLDCACHE -> ubuntu24-tap-genai-gcov_src (was ubuntu22-tap_src) - test cache key -> ubuntu24-tap-genai-gcov_test - MATRIX label gains ",genai-gcov" - "Run <group> tests" step exports COVERAGE=1 - Archive coverage report (LCOV .info) as artifact - Upload to Codecov tagged flags: tap-<group> The non-gcov ubuntu22-tap_src path is no longer referenced by any TAP group; CI-builds still produces it but it can be pruned in a follow-up once everything is observed green. The caller side (CI-<group>.yml on v3.0 declaring permissions: write-all so id-token:write propagates through the reusable call) is the companion change.	1 month ago
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	68d9f3e2c5	fix(ci): align Cache restore src path with CI-builds save path `actions/cache@v4` hashes the `paths`, `key`, and `enableCrossOsArchive` flag together into a "version" identifier. When save and restore disagree on paths, the version differs and the restore silently misses — even if the key matches an entry that plainly exists in the repo cache. ci-builds.yml saves `Cache save src` with: path: \| proxysql/src/ proxysql/lib/obj/.gcno The second entry was added so the `-gcov` variants can capture lib/obj/.gcno (needed by fastcov to map .gcda → source files). It's a no-op for non-gcov variants — the glob matches nothing — but it changes the computed version, so every restore step needs the same two-line path list to find the saved entry. `ci-legacy-g2-genai.yml` was already fixed and carries a comment documenting the gotcha. The other 47 test workflows still had only `proxysql/src/` on the restore side, producing "Failed to restore cache entry" on every PR. Aligning them with the save path here unblocks the test cascade across the board. ci-codeql.yml is left alone — its Cache restore src block is fully commented out, so there's nothing to align.	1 month ago
Rene Cannao	149d0cfba5	fix(ci): retry transient GHCR login + pull failures Observed failure (PR sysown/proxysql#5778, CI-mysql84-g9 run 25791456553, and earlier on CI-mariadb10-galera-g8 run 25782877144): Error response from daemon: Get "https://ghcr.io/v2/": net/http: request canceled (Client.Timeout exceeded while awaiting headers) ##[error]Process completed with exit code 1. The failure happens at the GHCR auth-token step inside `docker/login-action@v3` (or sometimes inside the subsequent `docker pull`). A single network blip against ghcr.io reds the whole TAP group, even though the test infrastructure itself is fine. Re-running the workflow then succeeds. Merge the previous two-step `Log in to GHCR` + `Pull CI base image` into one bash step wrapped in a 5-attempt retry loop with linear backoff (10s, 20s, 30s, 40s). On the first success, exit cleanly; on five consecutive failures, exit non-zero so the surfaced error is still loud rather than silently masking a real outage. Applied to all 41 reusable test workflows that pull `ghcr.io/sysown/proxysql-ci-base:latest`.	2 months ago
Rene Cannao	1d08f312d9	fix(ci): add GHCR authentication before docker pull GHCR packages are private by default. Add docker/login-action step to authenticate with GITHUB_TOKEN before pulling proxysql-ci-base in all 23 reusable workflows.	2 months ago
Rene Cannao	4d4bb823c8	perf(ci): pull pre-built proxysql-ci-base from GHCR instead of building Replace "docker build" of proxysql-ci-base in all 23 reusable workflows with "docker pull" from ghcr.io/sysown/proxysql-ci-base:latest. Eliminates apt-get update/install on every CI run, avoiding transient Ubuntu mirror sync failures and saving ~60s per job.	2 months ago
Rene Cannao	aa465bbc54	fix(ci): rename set_parser_algorithm=3 workflow to avoid Docker network issue	2 months ago

7 Commits (ci-pgsql-socket-g1)