Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.3k
test: skip IPv6 test on non-IPv6 systems#11432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Trott commented Feb 16, 2017 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Until recently, test-dgram-address would fail on IPv6 but still exit with a successful return code. (It would console.log() the error but not actually fail.) Now that the test has been updated such that it will fail the IPv6 part of the test if there is an error event emitted by the socket, skip the test on systems not equipped with IPv6.
Trott commented Feb 16, 2017
This fixes an issue that is currently causing CI to fail every time for two of the three Raspberry Pi setups we have in CI. I propose not waiting the 48 hours on this one and landing much sooner. /cc @nodejs/testing @cjihrig |
Trott commented Feb 16, 2017
rvagg commented Feb 16, 2017
Trott commented Feb 16, 2017
CI again (build failure on one host): https://ci.nodejs.org/job/node-test-pull-request/6456/ |
Until recently, test-dgram-address would fail on machines without IPv6 but still exit with a successful return code. (It would console.log() the error but not actually fail.) Now that the test has been updated such that it will fail the IPv6 part of the test if there is an error event emitted by the socket, skip the test on systems not equipped with IPv6. PR-URL: nodejs#11432 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
Trott commented Feb 17, 2017
Landed in d9a14b7 |
Until recently, test-dgram-address would fail on machines without IPv6 but still exit with a successful return code. (It would console.log() the error but not actually fail.) Now that the test has been updated such that it will fail the IPv6 part of the test if there is an error event emitted by the socket, skip the test on systems not equipped with IPv6. PR-URL: nodejs#11432 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
Until recently, test-dgram-address would fail on machines without IPv6 but still exit with a successful return code. (It would console.log() the error but not actually fail.) Now that the test has been updated such that it will fail the IPv6 part of the test if there is an error event emitted by the socket, skip the test on systems not equipped with IPv6. PR-URL: #11432 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Rod Vagg <[email protected]>
jasnell commented Mar 9, 2017
needs backport PRs in order to land on v6 or v4 |
Until recently, test-dgram-address would fail on machines without IPv6 but still exit
with a successful return code. (It would console.log() the error but not
actually fail.)
Now that the test has been updated such that it will fail the IPv6 part
of the test if there is an error event emitted by the socket, skip the
test on systems not equipped with IPv6.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
test dgram