From 6b4e413526c4305cd6c604072b8d3066519a549a Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 14 Nov 2018 22:53:59 +0000 Subject: [PATCH] doc: add help on fixing IPv6 test failures It took me a while to figure out the problem and then some googling to find the right answer. I think it is worth adding this to help other people in the future and to have an easy place to point people to for the solution if their test run fails with IPv6 failures. PR-URL: https://github.com/nodejs/node/pull/24372 Reviewed-By: Sakthipriyan Vairamani Reviewed-By: Luigi Pinca Reviewed-By: Franziska Hinkelmann --- BUILDING.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/BUILDING.md b/BUILDING.md index 63ddf8e7f4ff2a..50f2984d679274 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -253,6 +253,16 @@ $ ./node ./test/parallel/test-stream2-transform.js Remember to recompile with `make -j4` in between test runs if you change code in the `lib` or `src` directories. +The tests attempt to detect support for IPv6 and exclude IPv6 tests if +appropriate. If your main interface has IPv6 addresses, then your +loopback interface must also have '::1' enabled. For some default installations +on Ubuntu that does not seem to be the case. To enable '::1' on the +loopback interface on Ubuntu: + +```bash +sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=0 +``` + #### Running Coverage It's good practice to ensure any code you add or change is covered by tests.