The GitHub Actions job "Required Checks" on texera.git/main has succeeded. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: f32c974534e8a36f2510f90012b0191cad1cc70d / Yicong Huang <[email protected]> perf(ci): use postgres service container for python job (#4633) ### What changes were proposed in this PR? Switch the python job in `build.yml` from `apt-get install postgresql` + `systemctl start` to a `services: postgres` container, mirroring what the scala job already does: - Add `services.postgres` (image `postgres`, `POSTGRES_PASSWORD=postgres`, port 5432, `pg_isready` healthcheck). - Drop `Install PostgreSQL`, `Start PostgreSQL Service`, and the `sudo -u postgres psql -f` seed step. - Single `Create iceberg catalog database` step that runs `psql -h localhost -U postgres -f sql/iceberg_postgres_catalog.sql` (same pattern as the scala job). ### Any related issues, documentation, discussions? Closes #4634. Driven by repeated python-job failures on `apt-get update` against `azure.archive.ubuntu.com`, which has been unreliable; runs sit ignoring the InRelease responses for tens of seconds and either fail or surface stale package metadata. The docker registry path used by `services` is independent of that mirror. Side benefit: postgres container starts in seconds, vs. ~30 s of `apt-get update` even on a healthy day. Removes the only place in `build.yml` that still needed the apt mirror. ### How was this PR tested? Will be exercised by this PR's own python matrix once the CI runs. The seed SQL is the same one the scala job already runs successfully against the same container image. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.7 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/25239784635 With regards, GitHub Actions via GitBox
