test_async interferes with test_dblog. I solved this locally by shortening the sleep period, but that doesn't seem to be enough here. There should be a cleaner solution to isolate test_dblog.

The update_status calls from the async process do not seem to be captured by the logging database in the test suite.
This is explained here: https://www.sqlite.org/inmemorydb.html

Of course, all database connections sharing the in-memory database need to be in the same process

Ideas ?

Coverage increased (+0.5%) to 81.901% when pulling cbd1c29 on fix-656 into 7839f52 on main.

I just renamed the async test so its run at the end.

Note that some of the tests modify the CONFIG, and this has effects on the following tests. It would probably be best to make sure all tests that modify the config return it to its original state.

Note also that test_assync_inout is useless at the moment.

Hello,

I did a quick code review, imo you should split dca06fb

into:
Refactor test.create_sleep into test.Sleep
Change test_async to actually test asynchronous process.

and to split cbd1c29, with typo fix separated from the rest.

More over having a loop with proper status check instead of sleep(.5) maybe better in dca06fb

Replaced by #663 and #664