Cut PostgreSQL CI time: parallel builds and split qualification
Foundation / checks (ecs) (push) Successful in 5m55s
Foundation / checks (deploy) (push) Successful in 6m56s
Foundation / checks (tsan) (push) Successful in 9m35s
Foundation / checks (client) (push) Successful in 20m0s
Foundation / checks (network) (push) Successful in 22m38s
Foundation / checks (checks) (push) Successful in 44m57s
Foundation / checks (postgres) (push) Successful in 48m59s
Foundation / server-image (push) Successful in 40s
Foundation / image (push) Successful in 3m11s
Foundation / postgres-tools (push) Successful in 4m26s
Foundation / checks (ecs) (push) Successful in 5m55s
Foundation / checks (deploy) (push) Successful in 6m56s
Foundation / checks (tsan) (push) Successful in 9m35s
Foundation / checks (client) (push) Successful in 20m0s
Foundation / checks (network) (push) Successful in 22m38s
Foundation / checks (checks) (push) Successful in 44m57s
Foundation / checks (postgres) (push) Successful in 48m59s
Foundation / server-image (push) Successful in 40s
Foundation / image (push) Successful in 3m11s
Foundation / postgres-tools (push) Successful in 4m26s
Compile the PostgreSQL stages with PG_BUILD_JOBS=6 (was 2), including PostgreSQL itself. postgres-check.sh gains --full (release), --sanitizer (ASan: C++ suite plus backup/DR/upgrade process checks that run the instrumented binaries) and --suite-only (clang-tidy build), so SQL-only checks run once. Each run prints per-phase timings, and the postgres job logs runner CPU, memory and disk headroom. Also refresh the dev REGION_SESSION_WINDOW. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -136,7 +136,8 @@ runs. It works as follows:
|
||||
A scheduled CronJob, synced by Argo, follows once the destination exists.
|
||||
|
||||
**Qualification.** `tools/ci/backup-check.sh` runs inside `postgres-check.sh` for
|
||||
every PostgreSQL build:
|
||||
the release and ASan/UBSan PostgreSQL builds (the uninstrumented clang-tidy build runs
|
||||
only the C++ suite):
|
||||
- It backs up a real `evo-server` while the server commits under synthetic load.
|
||||
The backup head covers every acknowledgement made before the backup, and the
|
||||
source then moves past it.
|
||||
|
||||
Reference in New Issue
Block a user