-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Enable windows builds on appveyor #291
Labels
Comments
AdmiringWorm
added a commit
that referenced
this issue
Jul 21, 2020
Due to somehow the correct 'cwd' is not set when initialising the yeoman generators most of the unit tests fail because it can not locate the correct file to check. This commit changes this to specifically store the working directory every time a new generator is created. re #291
AdmiringWorm
added a commit
that referenced
this issue
Jul 21, 2020
Due to somehow the correct 'cwd' is not set when initialising the yeoman generators most of the unit tests fail because it can not locate the correct file to check. This commit changes this to specifically store the working directory every time a new generator is created. re #291
AdmiringWorm
added a commit
that referenced
this issue
Jul 21, 2020
Due to somehow the correct 'cwd' is not set when initialising the yeoman generators most of the unit tests fail because it can not locate the correct file to check. This commit changes this to specifically store the working directory every time a new generator is created. re #291
AdmiringWorm
added a commit
that referenced
this issue
Jul 21, 2020
Due to somehow the correct 'cwd' is not set when initialising the yeoman generators most of the unit tests fail because it can not locate the correct file to check. This commit changes this to specifically store the working directory every time a new generator is created. re #291
AdmiringWorm
added a commit
that referenced
this issue
Jul 21, 2020
Due to somehow the correct 'cwd' is not set when initialising the yeoman generators most of the unit tests fail because it can not locate the correct file to check. This commit changes this to specifically store the working directory every time a new generator is created. re #291
AdmiringWorm
added a commit
that referenced
this issue
Jul 22, 2020
Due to somehow the correct 'cwd' is not set when initialising the yeoman generators most of the unit tests fail because it can not locate the correct file to check. This commit changes this to specifically store the working directory every time a new generator is created. re #291
Been trying to enable this, but no matter what I try the build always hangs. NOTE: Appveyor have been completely disabled, plans are to enable builds on travis for windows instead (but there is the same problem with tests hanging). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to an unknown problem with the unit tests are hanging on appveyor windows builds, this image have been disabled on the ci cloud server.
This unit tests still works on a local windows installation, just not on appveyor.
Any help in resolving this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: