search

libp2p / js-libp2p-tcp

JavaScript implementation of the TCP module that libp2p uses that implements the interface-transport spec
https://libp2p.io
Other
76 stars 40 forks source link

CI IPv6 testing is unreliable #105

Closed jacobheun closed 2 years ago

jacobheun commented 5 years ago

Currently with the move to Travis CI, testing IPv6 addresses are unreliable.

Jorropo commented 5 years ago

@jacobheun I could add a cjdns node in the ci suite, is this a good enough solution for you ?

richardschneider commented 5 years ago

FYI: I've never got Travis CI to work with IPv6

See https://github.com/njh/travis-ipv6-test

Jorropo commented 5 years ago

I got it to work by playing with sysctl (in sudo mode) and cjdns. https://travis-ci.org/njh/travis-ipv6-test/jobs/545216549

jacobheun commented 5 years ago

@Jorropo would that enable us to run dial and listen tests in the suite? Right now the tests are only doing IPv4. I started work on improving IPv6 support for this but got blocked by the CI situation and then other priorities came up.

We are running a handful of things on Azure right now, and I believe they have better support for IPv6, although I haven't had a chance to test that more in depth yet, so that may be another option here.

Jorropo commented 5 years ago

@jacobheun yes, that fully allow test for ipv6 but you can't contact the real ipv6 internet, you have to do on hyperboria (a distributed meshed network) so if you want to conect to external node that only possible if they run cjdroute.

If you only use ::1 that fully works.

EDIT1: Mcast isn't avaible.

jacobheun commented 5 years ago

@Jorropo local ipv6 is all we need for this, so that's great, I'm not worried about any external testing for the suite.

achingbrain commented 2 years ago

Closing because this repo doesn't use travis for CI any more