39560518039
81%

Ran 21 Oct 2026 07:21AM UTC

Jobs 1

Files 236

Run time 1min

Badge

Embed ▾

Committed 21 Oct 2026 07:13AM UTC coverage: 80.315% (+0.2%) from 80.132%

Build # 39560518039

Build Type

push

github

Committed by

web-flow

Commit Message

test: explain read replica replay timeouts (#1141)

A PG18 CI job timed out after 60s waiting for the read replica to
replay WAL, while the same wait took about 1s in every other job:
https://github.com/supabase/etl/actions/runs/39548725394/job/119052760682

The panic only said "timed out", and the wait treated a failed
connection the same as slow replay, so the cause could not be told.

On timeout, report the last check (connection error, or recovery
state and replay LSN), the target LSN, and the replica's recovery,
startup process, WAL receiver, recovery conflict, and client session
state. The next failure should show whether replay stalled on a
conflict, the WAL receiver stopped, or the replica was unreachable.

Coverage Stats

56260 of 70049 relevant lines covered (80.32%)

42980.22 hits per line

Coverage Regressions

Lines	Coverage	∆	File
62	89.66	9.25%	crates/etl-destinations/src/ducklake/encoding.rs
21	84.86	0.78%	crates/etl-destinations/src/ducklake/batches.rs
1	98.0	-0.25%	crates/etl-destinations/src/ducklake/schema.rs

Jobs

ID	Job ID	Ran	Files	Coverage
1	39560518039.1	21 Oct 2026 07:21AM UTC	236	80.32	GitHub Action Run

supabase / etl / 39560518039
81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 39560518039

supabase / etl / 39560518039 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 39560518039

supabase / etl / 39560518039
81%

README BADGES
x