Skip to content
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

"InterfaceError: connection already closed" being raised when a test is run #326

Closed
rr- opened this issue Dec 7, 2018 · 1 comment · Fixed by #393 · May be fixed by #385
Closed

"InterfaceError: connection already closed" being raised when a test is run #326

rr- opened this issue Dec 7, 2018 · 1 comment · Fixed by #393 · May be fixed by #385

Comments

@rr-
Copy link

rr- commented Dec 7, 2018

This is the same as #198, #144, #127 and #167.

It all boils down to this:

As far as I'm concerned this should be using the same safety mechanism as the code in the original fix.

@andrlik
Copy link

andrlik commented May 31, 2019

Seconding this. Right now I'm having to do all sorts of monkeying around in my test suites to test the tasks independently and muting signals like crazy during other tests to prevent this issue from arising.

It's making it hard to get my test coverage to where it needs to be.

Urth added a commit to ossobv/django-q that referenced this issue Nov 27, 2019
When tasks run synchronously django-q should only affect the calling
context by running the tasks.
Fixes Koed00#326
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants