Uh oh!
There was an error while loading. Please reload this page.
doc: add help on fixing IPv6 test failures - #24372
Conversation
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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
mhdawson
commented
Nov 15, 2018
@vsemozhetbyt thanks for the review, accepted all of your suggestions. |
| on Ubuntu that does not seem to be the case. '::1' can be enabled on the | ||
| loopback interface on Ubuntu using: | ||
| `sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=0` |
There was a problem hiding this comment.
Nit: It would be better if we formatted this as console text, instead of inline code.
mhdawson
commented
Nov 15, 2018
@vsemozhetbyt any chance you can add your approval as well? |
Uh oh!
There was an error while loading. Please reload this page.
| The tests attempt to detect support for IPv6 and exclude IPv6 tests if | ||
| appropriate. However, 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. '::1' can be enabled on the |
There was a problem hiding this comment.
| on Ubuntu that does not seem to be the case. '::1' can be enabled on the | |
| on Ubuntu, that does not seem to be the case. '::1' can be enabled on the |
| appropriate. However, 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. '::1' can be enabled on the | ||
| loopback interface on Ubuntu using: |
There was a problem hiding this comment.
Replace the last sentence with this?
To enable '::1' on the loopback interface on Ubuntu:There was a problem hiding this comment.
I'm sure I had something like "You can .." but guidance is not to use you. :)
| appropriate. However, 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. '::1' can be enabled on the | ||
| loopback interface on Ubuntu using: |
Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>
mhdawson
commented
Nov 16, 2018
Comments addressed. Like CI run: https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/1632/ |
mhdawson
commented
Nov 16, 2018
CI good landing. |
Landed as 6b4e413 |
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>
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>
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>
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.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes