| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
CI failed to start. https://ci.nodejs.org/job/node-test-pull-request/2549/console LGTM if CI comes up green |
Sorry, something went wrong.
Sorry, something went wrong.
|
Added a fix-up for the CI hosts where localhost doesn't have an IPv6 address, PTAL. |
Sorry, something went wrong.
|
That only made it worse... @nodejs/build Can this be fixed on the buildbots? |
Sorry, something went wrong.
|
@bnoordhuis to be clear you want ::1 localhost into /etc/hosts rite? |
Sorry, something went wrong.
|
..or is it just whatever ::1 entry? debian8 on do has this: ::1 ip6-localhost ip6-loopback |
Sorry, something went wrong.
|
@jbergstroem Ideally, I'd like AAAA queries for localhost to resolve to ::1 everywhere. We currently have this list but trying them in order still doesn't make the tests pass on all machines, see e.g. debian8-x86 (but not debian8-64, oddly enough.) |
Sorry, something went wrong.
|
@bnoordhuis the reason they differ is because one is from DO and the other from softlayer. providers usually populate differently. I'll look at adding ::1 localhost to all hosts via the ansible-playbooks; but it might take a small while. |
Sorry, something went wrong.
|
I'm marking the tests as flaky on Linux for now, pending resolution of nodejs/build#415. New CI: https://ci.nodejs.org/job/node-test-pull-request/2815/ |
Sorry, something went wrong.
There was a problem hiding this comment.
Can you switch to the new common.skip().
Sorry, something went wrong.
|
LGTM with a couple comments. |
Sorry, something went wrong.
|
Good points. Updated with feedback. New CI: https://ci.nodejs.org/job/node-test-pull-request/2838/ EDIT: Make that https://ci.nodejs.org/job/node-test-pull-request/2839/ - I just landed #7037 to get the CI in a good state again. |
Sorry, something went wrong.
|
Still EADDRINUSE errors in https://ci.nodejs.org/job/node-test-commit-arm/3507/nodes=armv7-ubuntu1404/console. I guess the port could have still been in use from older CI runs. |
Sorry, something went wrong.
|
Should be better now. New CI: https://ci.nodejs.org/job/node-test-pull-request/2840/ |
Sorry, something went wrong.
|
All green now. |
Sorry, something went wrong.
Respect the `{ family: 6 }` address family property when connecting to
a remote peer over TLS.
Fixes: nodejs#4139
Fixes: nodejs#6440
PR-URL: nodejs#6654
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Update parallel/test-http-agent-getname to use assert.strictEqual() consistently and const-ify variables while we're here. PR-URL: nodejs#6654 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Respect the `{ family: 6 }` address family property when connecting to
a remote peer over TLS.
Fixes: nodejs#4139
Fixes: nodejs#6440
PR-URL: nodejs#6654
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Update parallel/test-http-agent-getname to use assert.strictEqual() consistently and const-ify variables while we're here. PR-URL: nodejs#6654 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Update parallel/test-http-agent-getname to use assert.strictEqual() consistently and const-ify variables while we're here. PR-URL: #6654 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Update parallel/test-http-agent-getname to use assert.strictEqual() consistently and const-ify variables while we're here. PR-URL: #6654 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Update parallel/test-http-agent-getname to use assert.strictEqual() consistently and const-ify variables while we're here. PR-URL: #6654 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Was previously 4.x for ES6 goodies. Now v4.5 to fix issues with TLS and IPv6 not playing nicely together, which meant that you couldn't connected to IRC networks over TLS with IPv6. See: - nodejs/node#6654
| Back | FazBrowse Home | New Git URL |
Respect the { family: 6 } address family property when connecting to
a remote peer over TLS.
Fixes: #6440
CI: https://ci.nodejs.org/job/node-test-pull-request/2549/