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

Travis tests failing #37

Open
mixmix opened this issue Jan 27, 2019 · 4 comments
Open

Travis tests failing #37

mixmix opened this issue Jan 27, 2019 · 4 comments

Comments

@mixmix
Copy link
Member

mixmix commented Jan 27, 2019

Tests pass locally, but the remote setup doesn't !

woop.

Looks like this (source)

> server started
Listening on :::8008 (multiserver net plugin)
Error: could not connect to sbot
    at /home/travis/build/ssbc/ssb-config/node_modules/ssb-client/index.js:100:23
    at /home/travis/build/ssbc/ssb-config/node_modules/multiserver/compose.js:66:24
    at Socket.<anonymous> (/home/travis/build/ssbc/ssb-config/node_modules/multiserver/plugins/net.js:42:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:66:8)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
  Error: connect EADDRNOTAVAIL :::8008 - Local (:::0)
    at internalConnect (net.js:964:16)
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:281:19)
    at net.js:1062:9
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at process._tickCallback (internal/process/next_tick.js:181:9)
@christianbundy
Copy link
Contributor

Is this because we're using :: rather than binding to 127.0.0.1? I saw a note in the comments that said something like "we're just using IPv4 because IPv6 breaks Travis" or something, but it looks like we've switched to IPv6 by default. Or maybe I'm misreading it?

@mixmix
Copy link
Member Author

mixmix commented Mar 7, 2019 via email

@dominictarr
Copy link
Contributor

I saw the heading and immediately thought ipv6, obviously.

@stale
Copy link

stale bot commented Jun 5, 2019

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale stale bot added the stale label Jun 5, 2019
@christianbundy christianbundy self-assigned this Jun 5, 2019
@stale stale bot removed the stale label Jun 5, 2019
@christianbundy christianbundy removed their assignment Jan 31, 2021
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

3 participants