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.

Sign up for GitHub

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

Jump to bottom

No Windows support #1

Closed
toolness opened this issue Sep 22, 2013 · 1 comment
Closed

No Windows support #1

toolness opened this issue Sep 22, 2013 · 1 comment

Comments

@toolness
Copy link
Owner

npm test doesn't even work because our setting of an environment variable in the command-line isn't understood.

Due to toolness/phantom-wd-runner#1, there's a phantomjs process lying around after the tests finish.

The ReDoS verifier also fails with a ENOENT from spawn.
@toolness
Copy link
Owner Author

I fixed toolness/phantom-wd-runner#1, so all core tests now pass, but bin/verify.js is still exiting with ENOENT on all problems.

toolness added a commit that referenced this issue Sep 22, 2013
@toolness
bin/verify.js now works on windows.
1a03135 
Helps with #1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toolness