'There is 1 other session using the database.'

[behave]

'There is 1 other session using the database.'

[dmwyatt]

I decided to look into this issue after just dealing with it for what seems like years.

What happens is that the tests run fine, but fail to delete the test database because of the other session(s) using database error. If you run the tests again, django prompts you to delete the test database before continuing. This is how I've always just dealt with it in the past.

All of my regular Django tests work fine, it is only tests run with behave-django that exhibit this issue.

• Django 2.1.4
• behave-django 1.1.0
• PostgreSQL 10.1

I'll try and remember to come up with a minimal reproducing project soon.

[dmwyatt]

I can't remember if this is the solution to the problem I had when I originally commented on this issue, but I came across this issue again in my Googlin' and this time I have a solution to a very similar issue...or maybe even the same issue.

Add conn_max_age=0 to your database configuration in tests. I figured this out from this answer on SO.

[bittner]

This is probably not related to behave-django as such. You'd have to provide more details, though, ideally steps to reproduce the error.

You may find more helpful hints in similar issues on the web, e.g.

• Django Test — Unable to drop and recreate test database (StackOverflow)
• https://code.djangoproject.com/ticket/22420
• Fantomas42/django-blog-zinnia#476
• Concurrent Jenkins builds of a Django application (a blog)
• grosser/parallel_tests#412

The last issue suggests that the problem is related to Postgres alone, not even Django. At least the error message comes directly from there. Some other application may use your database while you run the tests.

Please let us know when you find the culprit, so others can profit too. I leave the issue open in the meantime.

[bittner]

Closing this issue for lack of activity.

[bittner]

That sounds like an interesting background for learning more about the issue. (Thanks for digging!)

Please also mention any other technology that may be involved (e.g. Selenium) and the environment that the failing tests are run in. (I guess, a successfully failing test project to reproduce the issue will exhibit all of that.)

behave-django isn't much "magic", it's mostly just glue code between test tools. I wouldn't be surprised to find a generic issue that can be reproduced without behave-django.

[nhill-cpi]

@dmwyatt Did you look into this more? Just wondering b/c I'm running into the same error.

[dmwyatt]

No, I got caught up in another project that doesn't use behave. Once I get back to a behave-using project I'll be able to investigate.

[bittner]

Thanks @dmwyatt!

Details to this setting are available from the Databases section in Django's documentation.

I'm closing this issue as sufficiently discussed.