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

TravisCI breaks with EADDRNOTAVAIL #1545

Closed
hekike opened this issue Nov 1, 2017 · 1 comment
Closed

TravisCI breaks with EADDRNOTAVAIL #1545

hekike opened this issue Nov 1, 2017 · 1 comment

Comments

@hekike
Copy link
Member

hekike commented Nov 1, 2017

Bug Report

master tests pass on a local machine but break on TravisCI:

server.test.js / gh-751 IPv4/IPv6 server URL

Error: listen EADDRNOTAVAIL ::1:36480
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Server._listen2 (net.js:1249:19)
    at listen (net.js:1298:10)
    at net.js:1408:9
    at _combinedTickCallback (internal/process/next_tick.js:83:11)
    at process._tickDomainCallback (internal/process/next_tick.js:128:9)

Node.js Version

all

Repro case

See: https://travis-ci.org/restify/node-restify/jobs/295430142

Are you willing and able to fix this?

Yes, but I need a hint

@hekike hekike mentioned this issue Nov 1, 2017
4 tasks
@hekike hekike changed the title Test broken on TravisCI due EADDRNOTAVAIL TravisCI breaks with EADDRNOTAVAIL Nov 1, 2017
@hekike
Copy link
Member Author

hekike commented Nov 2, 2017

Seems to be that the current version of TravisCI lacks the IPv6 support:

The virtual machines in the Legacy environment running the tests have IPv6 enabled. They do not have any external IPv4 address but are fully able to communicate with any external IPv4 service. The container-based, OS X, and GCE (both Precise and Trusty) builds do not currently have IPv6 connectivity. - https://docs.travis-ci.com/user/reference/precise/#Networking

TravisCI's migration announcement from 2015-11-27:

The major change that is coming with this migration is that local and external IPv6 networking will no longer be present. This has been present and while technically not considered to be a feature, it has been available. With the move to GCE this will no longer work, until such time as as GCE adds IPv6 support - https://blog.travis-ci.com/2015-11-27-moving-to-a-more-elastic-future

Related GCE docs:

Each instance can only belong to one network. All VPC networks use the IPv4 protocol. Compute Engine networks currently do not support IPv6. However, Google is a major advocate of IPv6 and it is an important future direction. - https://cloud.google.com/compute/docs/networks-and-firewalls#networks

I'm not sure why we have this issue now. cc @yunong

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

No branches or pull requests

1 participant