-
Notifications
You must be signed in to change notification settings - Fork 90
"Possibly failed to run initdb" - Windows #136
Comments
There is a problem with starting instance of postgres process. |
I wonder if it would be possible to detech if MSVCR120 is missing and print a warning, rather than have nothing printed to console and no error shown at all. |
Perhaps what would also help is adding support for capturing the output of from the commands run or checking the exit code and printing what command failed. Currently under windows nothing is printed at all making debugging hard. |
I've faced with the same problem. Could you please increase priority of this issue? |
I am trying to run tests using an embedded postgres server, but the process just hangs indefinitely after it extracts the archive and runs all the insert statements. There's one small Warning line that states
Possibly failed to run initdb
, but provides no further information about what went wrong or whether it actually failed to run and if that's what the problem is. Is there any way I can debug this?The text was updated successfully, but these errors were encountered: