chore: stop running postgres-only tests if DB is not set #18784
Merged
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.
Fixes coder/internal#695
PostgreSQL tests are getting run in a non-postgres CI job because the tests don't get skipped if the
DB=
env is unset. This PR adds a skip for them.They are flaking in the
test-go-race
CI job. They run fine in thetest-go-race-pg
job, which pre-creates the postgres server, so the flakiness is almost certainly related to spinning up the database server.