Richard Tibbles

This work should be targeted to develop and targeted there, as this version of pytest is not compatible with Python 2.7, which has been dropped in develop.

Interesting - there must be something else at play here. One possibility is a change in pytest that is causing state to be persisted between tests. Seeing the traceback from...

That's some good debugging - I notice that the test_content_sync_hook test case inherits from the test_content_request testcase: https://github.com/learningequality/kolibri/blob/develop/kolibri/core/content/test/test_content_sync_hook.py#L12 So it may be that this is the cause of the interaction?...

Sorry @thesujai I missed the follow up comments here as I was out of the office. It looks like the dbrestore tests might be fixable by tweaking the configuration for...

Once we have merged [this PR](https://github.com/learningequality/kolibri/pull/11974) (which upgrades Django to 3.2), it would be good to rebase this PR onto develop, as that may help with some of the errors.

I have rebased this PR onto latest develop and pushed, let's see how the tests shake out now!

No - it doesn't seem to have helped. Although, you had mentioned above that there was some configuration change needed for the upgraded pytest-django plugin?

Yes, I have the overall issue for upgrading to support Python 3.12, which this is a prerequisite for.

The main novel thing I am seeing in here that I've not seen in other logs is this: ``` WARNING 2024-02-14 10:07:45,480 zeroconf Exception occurred: Traceback (most recent call last):...

The other notable errors here seem to be due to database contention - either database locked errors on the default database, or other issues with writing on the task database....