Problem running tox on hyperkitty

I am trying to run
tox -e py35-django111
on HyperKitty. I run into an issue in that the tests run up to a point after which all but the last 2 fail with a "too many open files" exception. These files are logs created in directories /tmp/hyperkitty-testing-*, and over 100 /tmp/hyperkitty-testing-* directories are left behind. This is with an open file limit of 1024.
If I raise the limit to 4096, everything runs and no /tmp/hyperkitty-testing-* directories are left behind, but it seems perhaps hyperkitty/tests/utils.TestCase._post_teardown() should have something added to undo what hyperkitty/tests/utils.setup_logging() sets up.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On Mon, Mar 19, 2018, at 3:30 PM, Mark Sapiro wrote:
Thanks a lot to find the real reason for this problem. I did find this problem when I was working on the Python 3 port but couldn't really pin-point the real reason for why is this happening.
-- Abhilash Raj maxking@asynchronous.in

On 19.03.2018 23:30, Mark Sapiro wrote:
It might look like that but the logs are not the actual problem as those files are properly closed after the test finishes.
I tried to disable logging to files all together but the problem persisted.
The real cause for the excessive number of file descriptors is django-q, which creates opens lots and lots of files (for inter process communication?).
Best Leon

On Tue, Mar 20, 2018, at 5:57 AM, Leon Merten Lohse wrote:
It was trying to create File Descriptors and failing every time, but I am not 100% sure if that itself is the reason for this. It could be, but I can't replicate this issue easily, maybe filing a bug with django-q and seeing what they think might be worthwhile?
-- Abhilash Raj maxking@asynchronous.in

On Mon, Mar 19, 2018, at 3:30 PM, Mark Sapiro wrote:
Thanks a lot to find the real reason for this problem. I did find this problem when I was working on the Python 3 port but couldn't really pin-point the real reason for why is this happening.
-- Abhilash Raj maxking@asynchronous.in

On 19.03.2018 23:30, Mark Sapiro wrote:
It might look like that but the logs are not the actual problem as those files are properly closed after the test finishes.
I tried to disable logging to files all together but the problem persisted.
The real cause for the excessive number of file descriptors is django-q, which creates opens lots and lots of files (for inter process communication?).
Best Leon

On Tue, Mar 20, 2018, at 5:57 AM, Leon Merten Lohse wrote:
It was trying to create File Descriptors and failing every time, but I am not 100% sure if that itself is the reason for this. It could be, but I can't replicate this issue easily, maybe filing a bug with django-q and seeing what they think might be worthwhile?
-- Abhilash Raj maxking@asynchronous.in
participants (3)
-
Abhilash Raj
-
Leon Merten Lohse
-
Mark Sapiro