Uh oh!
There was an error while loading. Please reload this page.
test(stack): stabilize postgres persistence e2e - #6175
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:16fb0792ce
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:c9791ebbf0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Uh oh!
There was an error while loading. Please reload this page.
TL;DR
Stabilize the Postgres persistence e2e by checking only the Docker containers created during native stack startup.
The test previously checked every matching container on the runner. A container left by another test could therefore cause a failure even when native startup used no Docker containers.
Capture matching container IDs before startup and assert that no new IDs appear afterward.
This follows the stack test suite's existing snapshot and diff pattern while preserving Docker startup and data persistence coverage...
ref:
spotted on: https://github.com/supabase/cli/actions/runs/31634963213/job/94242831412