Skip to content

tests: Explicitly close async database pools within the context of a tokio runtime #8382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 29, 2024

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Mar 29, 2024

Without this, the Drop implementation of the the pool would complain about not running within a tokio runtime and ultimately panic the tests. This only happened to work so far because none of our integration tests had used the async database pool yet.

…tokio runtime

Without this, the `Drop` implementation of the the pool would complain about not running within a tokio runtime and ultimately panic the tests. This only happened to work so far because none of our integration tests had used the async database pool yet.
@Turbo87 Turbo87 added C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear A-backend ⚙️ labels Mar 29, 2024
@Turbo87 Turbo87 merged commit 0e080a6 into rust-lang:main Mar 29, 2024
@Turbo87 Turbo87 deleted the deadpool-cleanup branch March 29, 2024 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant