Comment 0 for bug 1506091

Revision history for this message
Eva Balycheva (ubershy) wrote :

Example of affected test class: https://github.com/openstack/zaqar/blob/master/zaqar/tests/unit/transport/websocket/v2/test_messages.py

After executing this test, the database still remains in filesystem, consuming space.
It's because the database is not being dropped by the tearDown() method.
As you can see, the tearDown() method just removes the created queue from the database.

Though pools and catalogue databases are always dropped by the parent test class, if polling was enabled:
https://github.com/openstack/zaqar/blob/master/zaqar/tests/unit/transport/websocket/base.py#L52

I think the right way is not to remove information from databases, but just to drop the databases with all information they had.

But maybe such behavior was implemented on purpose and I just don't see a good reason for it.

Fixing this bug will require a plenty of work, but...
1. Is it really a bug?
2. If yes, should this bug be fixed by the way I propose?

Please leave your thoughts in comments.