36991004075
67%
develop: 67%

Ran 02 Oct 2026 09:40AM UTC

Jobs 1

Files 79

Run time 1min

Badge

Embed ▾

Committed 02 Oct 2026 09:35AM UTC coverage: 66.737%. Remained the same

Build # 36991004075

Build Type

push

github

Committed by

web-flow

Commit Message

test(stack): ignore the host-gateway probe when listing whole-stack workloads (#6952)

The Docker whole-stack E2E "eager lifecycle and reopen" failed
intermittently on its identity check
(`identity.endsWith(databaseMarker)` in
`tests/whole-stack/scenarios.ts`).

`tests/whole-stack/workloads.ts` listed Docker workloads by the
`com.supabase.stack` label alone. The container runtime's host-gateway
probe (`readProbeHosts` in `Container.ts`) is a short-lived `docker run
--rm` container that carries the stack labels but deliberately no
`com.supabase.instance` label, since it isn't an instance. When the
listing ran while the probe was still exiting, the probe's bare
container ID was taken as a workload identity. Running the probe command
in a loop while polling the same `docker ps` filter catches it
mid-flight on most iterations.

The listing now only counts containers carrying `com.supabase.instance`
or `com.supabase.stack-managed=true`, which are the labels that identify
stack workloads. The probe still removes itself, so the check that every
workload is gone at stop keeps its coverage. Product code is unchanged.

Coverage Stats

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	36991004075.1	02 Oct 2026 09:40AM UTC	79	66.74	GitHub Action Run

supabase / cli / 36991004075
67%
develop: 67%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 36991004075

supabase / cli / 36991004075 67% develop: 67%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 36991004075

supabase / cli / 36991004075
67%
develop: 67%

README BADGES
x