Skip to content

Directory cached_data_dir did not cleanup after test finished #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sfalkon opened this issue Oct 24, 2017 · 5 comments
Closed

Directory cached_data_dir did not cleanup after test finished #27

sfalkon opened this issue Oct 24, 2017 · 5 comments
Labels

Comments

@sfalkon
Copy link

sfalkon commented Oct 24, 2017

Directory cached_data_dir did not cleanup after test finished

@funbringer funbringer added the bug label Oct 24, 2017
@funbringer
Copy link
Collaborator

Hi @sfalkon, good catch!

@funbringer
Copy link
Collaborator

funbringer commented Oct 24, 2017

@ildus, @zilder, I think we should remove cached_data_dir automatically, but it's hard to tell who should be responsible for this action. We could probably add a refcounter and do +1 in __enter__() and -1 in __exit__() of PostgresNode, but that would nullify all the benefits of such cache if only one instance of PostgresNode is active at any time.

@ildus
Copy link
Collaborator

ildus commented Oct 25, 2017

@funbringer yeah, we can't remove it on __exit__. First of all we will need it for the next node, and secondly user can start nodes without with blocks. I think we should use atexit handlers.

@stalkerg
Copy link
Contributor

stalkerg commented Oct 25, 2017

Maybe, should user call "clean()" function manually?

@funbringer
Copy link
Collaborator

Fixed in 1.3.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants