Skip to content

Set django-q logging level to ERROR for tests

David Runge requested to merge dvzrv/hyperkitty:issues/330 into master

hyperkitty/tests/settings_test.py: When using django-q with the "sync": True configuration option, while setting its logging level to "WARNING" the test suite generates large output (several Mb!) with the following message:

Preserving django database connections because sync=True. Beware that
tasks are now injected in the calling context/transactions which may
result in unexpected bahaviour.

As this behavior makes CI pipelines fail (due to logs being to large) and is heavy on downstreams packaging hyperkitty and running tests, the logging level is set to "ERROR" in this commit.

Fixes #330 (closed)

Merge request reports