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: #24372 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
nodejs · Nov 14, 2018 · 5f747f1dc56a59573e056946c016b4b588e9e80e · 5f747f1
1 parent 331b26e
commit 5f747f1dc56a59573e056946c016b4b588e9e80e
Unified Split

Showing with 10 additions and 0 deletions.

+10 −0 BUILDING.md
diff --git 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.