Skip to content

Commit 5f747f1

Browse files
mhdawsonrvagg
authored andcommitted
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>
1 parent 331b26e commit 5f747f1

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

BUILDING.md

+10
Original file line numberDiff line numberDiff line change
@@ -253,6 +253,16 @@ $ ./node ./test/parallel/test-stream2-transform.js
253253
Remember to recompile with `make -j4` in between test runs if you change code in
254254
the `lib` or `src` directories.
255255

256+
The tests attempt to detect support for IPv6 and exclude IPv6 tests if
257+
appropriate. If your main interface has IPv6 addresses, then your
258+
loopback interface must also have '::1' enabled. For some default installations
259+
on Ubuntu that does not seem to be the case. To enable '::1' on the
260+
loopback interface on Ubuntu:
261+
262+
```bash
263+
sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=0
264+
```
265+
256266
#### Running Coverage
257267

258268
It's good practice to ensure any code you add or change is covered by tests.

0 commit comments

Comments
 (0)