Closed denisri closed 10 months ago
This is not so trivial. More generally, it is a bit complex to know when to automatically create and destroy a database to cover all use cases. Info in config (including /tmp/capsul_engine_database.rdb
in default config) is a meeting point for all database users. If a new path is used each time, there will be no more connection between various users (i.e. test script and corresponding workers). I suppose that the problem arise when a test create the database server and start workers. One of the worker will have the responsability to ask the server to stop, just before that, it put the server in the "shutting down" state. Since these two steps are not atomic, there is a possibility that the next test ask for database creation between them and fail.
There are several possibilities to solve this depending on what we expect from default database and how do we want to test database (using the default path or an explicit one).
I hope this is fixed by the last commit.
Tests in capsul v3 often fail randomly with the following error:
and:
Probably because the same file
/tmp/capsul_engine_database.rdb.socket
is reused. We should use real generated and unique temp filenames.