-
Notifications
You must be signed in to change notification settings - Fork 44
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
Windows support #303
Comments
@pernlofgren I see there two issues, one is related to pytest-postgresql, the other to mirakuru ( ClearcodeHQ/mirakuru#392 ). In both cases, I have no resources (time and material) to develop and maintain windows solutions by myself. And to accept both solutions I'd need to have CI that runs tests against windows. I'd be happy to accept help in both cases though. |
Thanks for the reply @fizyk. Unfortunately we are in the same boat with not enough resources at the moment. We have switched to using postgresql_noproc for our Windows users and this is working as expected. Will let you do what you want with this issue 😅 |
Should be easier to handle since pytest-postgresql CI got moved to github actions. Now it's a matter of adding a workflow for windows and fix issues there |
As a quick fix until the issue is resolved, you could add the following to your conftest.py:
|
Tried the above fix but didn't work on Github Actions:
|
What action do you want to perform
Hi, we are wanting to use the postgresql_proc fixture in our test suite and we ran into a few errors. Version 2.4.0 on Windows 10 and PostgreSQL version 11.
What are the results
On the creation of PostgreSQLExecutor we find it errors when calling pg_ctl due to the quotes around stderr on this line , seems Windows is not happy. By removing the quotes it managed to set up the database and run the test suite.
However it now runs into the problem of not being able to stop with
os.killpg
, as this function doesn't exist for Windows.What are the expected results
We were wondering if others have run into this issue too and if there's a way to get this fix in. Any help is appreciated as its a great plugin to use!
The text was updated successfully, but these errors were encountered: