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

Add Node.js 8 to Travis CI test matrix #115

Merged
merged 1 commit into from
Jun 15, 2017
Merged

Conversation

watson
Copy link
Collaborator

@watson watson commented Jun 15, 2017

The tests are currently failing on Node.js 8 and I'm not that familiar with the test suite yet, so I need some help reading the output and hopefully making the tests pass.

There's already a PR open that fixes some of the tests, but not all of them (#110).

If someone could explain how to interpret the error output from the tests, it would be awesome 😃

@hayes
Copy link
Collaborator

hayes commented Jun 15, 2017

Looks good to me

@hayes hayes merged commit c92d2e1 into othiym23:master Jun 15, 2017
@watson watson deleted the node8 branch June 16, 2017 11:11
@watson
Copy link
Collaborator Author

watson commented Jun 16, 2017

@hayes I probably didn't explain my self very well, but I wanted to fix the Node.js 8 bugs before merging this. I can see that you opened #118 to revert this, but it was closed instead of being merged?

I think it's better to revert so that other PR's don't have to spend time debugging a false positive.

@watson watson restored the node8 branch June 16, 2017 11:22
@hayes
Copy link
Collaborator

hayes commented Jun 16, 2017

@watson this was my bad, I misinterpreted the failures as being related to the same node bug that was affecting v7. I am hoping to just get the test fix for. Node 8 merged today, but if you think it would be better to revert I would be happy to do that. I still have a little digging to do too understand why the results are a little different

@watson
Copy link
Collaborator Author

watson commented Jun 16, 2017

Nah, I didn't expect a fix for 8 so soon, so if we are close to merging then let's just keep 8 in master

@watson watson deleted the node8 branch June 16, 2017 13:25
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.

2 participants