-
Notifications
You must be signed in to change notification settings - Fork 698
Test in Node 0.12 and io.js #468
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
Conversation
|
👍 |
|
https://travis-ci.org/nodegit/nodegit/jobs/53249611#L528 I'm going to cancel and restart this in Travis |
|
Interesting... it didn't queue up on Travis. |
|
Right? o.O |
|
W/e, just reset to the prior commit and recommitted the same changes. |
|
I'm switching us over to use https://github.com/rvagg/pangyp until nodejs/node-gyp#564 is merged. Reference: nodejs/node#433 |
Currently there's a PR (nodejs/node-gyp#564) that's awaiting a merge that will allow us to once again use node-gyp to compile nodegit across all platforms. Until that is merged however we can use pangyp as a stop-gap. After that PR is merged though we should switch back to node-gyp.
ea11429 to
c59309c
Compare
|
We might want to bump up timeouts on our CI tests since Travis has been running slow lately. |
|
Pretty sure this was the issue. |
|
Getting |
|
pangyp currently doesn't work in windows for iojs :( |
|
Should we just keep going on with the caveat of "Does not work in iojs for windows right now"? |
|
Yup, works well for me! |
Test in Node 0.12 and io.js
No description provided.