hyperledger / fabric-x-committer / 22956400699 / 2
90%
main: 91%

LAST BUILD BRANCH: fix/696-integration-port-reservation
DEFAULT BRANCH: main
Ran
Files 122
Run time 3s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 83.197% (-0.05%) from 83.244%
22956400699.2

Pull #423

github

cendhu 
Use navitve PostgreSQL credentials and fix PG 18 compatibility issues

 Summary

  - Switch PostgreSQL test containers from reusing YugabyteDB's yugabyte/yugabyte credentials to PostgreSQL's native
  postgres/postgres defaults
  - Fix TLS certificate permission issues that prevented tests from passing on Docker Desktop and Podman Desktop
  (macOS/Windows)
  - Fix race condition in the SSL enforcement script caused by PostgreSQL 18's changed PGDATA layout and two-phase startup

  PostgreSQL 18 Changes That Drove This

  PostgreSQL 18 changed the default PGDATA directory from /var/lib/postgresql/data to /var/lib/postgresql/<major>/docker
  (e.g. /var/lib/postgresql/18/docker). This broke hardcoded paths in the SSL enforcement script. Additionally, PostgreSQL 18
   Alpine images no longer create the Unix socket at the default port during initdb, causing psql commands that rely on
  socket-based connections to fail during the entrypoint's two-phase startup (temp server on port 5432, real server on the
  configured port).

  Changes

  1. Native PostgreSQL credentials (postgres/postgres)

  Previously, PostgreSQL containers reused YugabyteDB's yugabyte/yugabyte credentials via POSTGRES_USER=yugabyte. This caused
   a race condition: the PG Docker entrypoint creates custom users/databases after initdb, but pg_hba.conf readiness checks
  could trigger before that step completed, leading to FATAL: database "yugabyte" does not exist.

  The postgres user and database always exist immediately after initdb (they are PostgreSQL built-ins), eliminating the race
  entirely. testdb.NewConnection() now accepts a dbType parameter and returns the correct default credentials for each
  database engine.

  POSTGRES_USER is omitted from the environment because postgres is PostgreSQL's built-in default superuser — the Docker
  image defaults to postgres when the variable is not set.

  2. TLS certificate entrypoint wrapper

  Docker Desktop and Podman Desktop run container... (continued)
Pull Request #423: [dependency] upgrade to latest stable postgres

8729 of 10492 relevant lines covered (83.2%)

0.91 hits per line

Source Files on job db-test - 22956400699.2