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 10 to CI matrices and update tests to account for changes in node.js 10 #279

Merged
merged 5 commits into from
May 16, 2018

Conversation

tolbertam
Copy link
Contributor

Adds node.js 10 to our test matrices.

Also makes a number of test changes:

  • Use 192.0.2.1 in EC2MultiRegionTranslator test. 127.100.100.1 resolves by default in Ubuntu 17.04+ so using a reserved address seemed more reliable.
  • Fixed assert.throws use as nodejs 10 will now fail when using string for validating expectation.
  • Account for node.js 10 change to defer readable events to nextTick.

Using a local address may resolve to localhost depends on DNS
configuration.  i.e. systemd-resolved adds a 127.0.0.53 dns server in
ubuntu 17.0.4+ that would resolve 127.100.100.1 to localhost.
Validate on expected Error instead of expected message to avoid
ERR_AMBIGUOUS_ARGUMENT.
As of node 10, all 'readable' events are deferred to nextTick.  See
nodejs/node@1e0f3315c7 for more info.
Also run integration tests with node 8 instead of 6 in appveyor
@jorgebay
Copy link
Contributor

I imagine finding the underlying issue for stream-based test was a tough one :) nodejs/node#17979

Great fixes! +1

@tolbertam
Copy link
Contributor Author

Indeed it was! I ultimately found the notice about it in the release notes:

  • The 'readable' event is now always deferred with nextTick. [1e0f3315c7]

But it was definitely puzzling at first 😄

@tolbertam tolbertam merged commit 707953f into master May 16, 2018
@tolbertam tolbertam deleted the nodejs-10 branch May 16, 2018 14:33
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