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

Fix windows spawn #38

Merged
merged 3 commits into from
Aug 2, 2015
Merged

Conversation

rmg
Copy link
Contributor

@rmg rmg commented Jul 31, 2015

This doesn't fix the problem of coverage not working on Windows, and it isn't a complete fix to the general problem of running on Windows, but if tap is upgraded to a version of nyc with this fix applied it should at least stop crashing on Windows when tap --coverage is run.

It may even fix #26

/cc @sam-github @isaacs

rmg added 3 commits July 31, 2015 12:31
Under Windows, the js file isn't executable.
Things like the name of the checkout or the path separators can change.
@rmg rmg mentioned this pull request Jul 31, 2015
@bcoe
Copy link
Member

bcoe commented Aug 1, 2015

@rmg thanks, any thoughts as to why the coverage reports themselves ain't workin' on Windows? spawn-wrap related perhaps?

@rmg
Copy link
Contributor Author

rmg commented Aug 1, 2015

@bcoe I spent a while digging through it but couldn't seem to get past this, but I was only looking at this module (I don't have a real Windows dev environment, so working with multiple repos was too annoying). I assume it is related to path separators being translated in some places and preserved in others.

bcoe added a commit that referenced this pull request Aug 2, 2015
@bcoe bcoe merged commit 31f65b9 into istanbuljs:master Aug 2, 2015
@bcoe
Copy link
Member

bcoe commented Aug 2, 2015

@rmg released in nyc@3.1.0.

@rmg rmg deleted the fix-windows-spawn branch August 19, 2015 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fails when running npm test
2 participants