fix: flake check was broken/could not start postgres #1063
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Sam Rose <samuel@supabase.io>
pcnc
approved these changes
Jul 20, 2024
damonrand
pushed a commit
to cepro/postgres
that referenced
this pull request
Jun 15, 2025
* fix: flake check was broken/coul not start postgres * fix: buildFeature missing at least auth0_fdw (supabase#1064) Co-authored-by: Sam Rose <samuel@supabase.io> --------- Co-authored-by: Sam Rose <samuel@supabase.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
flake check was not running in some contexts
Add some more settings to nail down specifics when running
Give an arbitrary key for this testing context (but not for other flake apps)