Skip to content
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

Open
AdmiringWorm opened this issue Mar 28, 2020 · 1 comment
Open

Enable windows builds on appveyor #291

AdmiringWorm opened this issue Mar 28, 2020 · 1 comment
Labels
build help wanted Extra attention is needed

Comments

@AdmiringWorm
Copy link
Member

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.

@AdmiringWorm AdmiringWorm added help wanted Extra attention is needed build labels Mar 28, 2020
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
@AdmiringWorm
Copy link
Member Author

Been trying to enable this, but no matter what I try the build always hangs.
To get this working I would need to get some help on this.

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
Labels
build help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant