Fix PostgreSQL connection leak in test environment #683
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.
Job tests were causing PostgreSQL connection leaks in CI, failing with 583 test failures due to exhausted connections.
Root Cause
The application uses GoodJob as the ActiveJob adapter globally. GoodJob maintains a separate database connection pool that persists across inline job executions in tests, preventing proper connection cleanup.
Changes
:testadapter instead of GoodJobconfig.active_job.queue_adapter = :testtoconfig/environments/test.rbThe
:testadapter executes jobs inline without a separate connection pool, ensuring connections are properly returned after each test.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.