| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
CI: https://ci.nodejs.org/job/node-test-pull-request/10909/ (do we have one for the internet tests?) |
Sorry, something went wrong.
There was a problem hiding this comment.
I am not quite sure if common/dns is the best place to put this. Also pending docs.
Sorry, something went wrong.
There was a problem hiding this comment.
If it’s specific to test/internet, it might be better live in a file there (similar to what test/async-hooks has)?
Sorry, something went wrong.
There was a problem hiding this comment.
I'm not 100% sure about that... On the one hand, I'd rather see all "harness" code in common, on the other hand this should not be used by any other suite.
/ping @Trott & @nodejs/testing
Sorry, something went wrong.
There was a problem hiding this comment.
Alternatively just add another module, test/common/internet.js
Sorry, something went wrong.
There was a problem hiding this comment.
I'm not 100% sure about that... On the one hand, I'd rather see all "harness" code in common, on the other hand this should not be used by any other suite.
I think it's not a terrible bad idea to replace other google.com references in parallel tests..also when my ISP DNS hijacks NXDOMAIN there are constant errors from parallel/test-net-connect-immediate-finish and parallel/test-net-better-error-messages-port-hostname, it would be helpful to replace those this.hostname.is.invalid with *** configured via environment variables.
Sorry, something went wrong.
There was a problem hiding this comment.
💯
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with docs.
Sorry, something went wrong.
There was a problem hiding this comment.
Improving the test at the same time? Nice!
Sorry, something went wrong.
There was a problem hiding this comment.
@gibfahn There are so many missing common.mustCall in the internet tests...better leave it to other PRs but this is in a loop, so I thought why not :D..
Sorry, something went wrong.
Nope, added to #16390 (comment) |
Sorry, something went wrong.
Do all these defaults now work behind the GFW? |
Sorry, something went wrong.
|
@gibfahn In my case it works reliably when using the 114 DNS(114.114.114.114) or the Google Public DNS(8.8.8.8, I am surprised to find that it is accessible from my ISP again). Other popular public DNS behind GFW like AliDNS and DNSPod DNS all miss some records tested by test-dns.js from time to time. With the DNS servers designated by my ISP it never works, I will have to set up those env vars using hosts behind GFW. DNS hijacking is very common behind GFW and the situation varies among different ISP and regions. Also, setting up the system to use public DNS servers does not guarantee you are actually connecting to their servers, some ISP hijacks requests to popular public DNS servers (there are traceroute reports showing that from time to time). (FWIW, I am with China Mobile in Hangzhou when I work on this PR). |
Sorry, something went wrong.
There was a problem hiding this comment.
How about coalescing the params?
Sorry, something went wrong.
There was a problem hiding this comment.
How about defining a constant for 0.0.0.0 as well?
Sorry, something went wrong.
There was a problem hiding this comment.
How about defining a constant for ::1 as well?
Sorry, something went wrong.
There was a problem hiding this comment.
localhost is defined for IPv4 and IPv6:
Lines 183 to 185 in 27e12e7
Sorry, something went wrong.
There was a problem hiding this comment.
I am not sure about the locality and proximity of our test systems w.r.t the system that hosts http://nodejs.org . If they are too close / under one subnet etc. how some of the tests (like dns resolution, pings, downloads etc.) are going to respond in terms of network level operations - will there be any bypasses?
Sorry, something went wrong.
|
@refack @addaleax @gibfahn @gireeshpunathil I've move the addresses to a new module test/common/internet.js and added documentation, PTAL. I'll defer the other constants e.g. 0.0.0.0 to another PR (looks like a good first issue). |
Sorry, something went wrong.
There was a problem hiding this comment.
Nit: Can you please add an entry for this new module to the table of contents near the start of this file?
Sorry, something went wrong.
There was a problem hiding this comment.
@Trott Of course!
Sorry, something went wrong.
This commit introduces test/common/internet.address, which includes a set of addresses for doing internet tests. These addresses can be overriden using NODE_TEST_* environment variables.
This commit introduces test/common/internet.address, which includes a set of addresses for doing internet tests. These addresses can be overriden using NODE_TEST_* environment variables. PR-URL: #16390 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #16390 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed in f2cb78c...5dca787, thanks! |
Sorry, something went wrong.
This commit introduces test/common/internet.address, which includes a set of addresses for doing internet tests. These addresses can be overriden using NODE_TEST_* environment variables. PR-URL: #16390 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #16390 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Should this be backported to v6.x-staging or v8.x-staging? If yes please follow the guide and raise a backport PR, if not let me know or add the dont-land-on label. |
Sorry, something went wrong.
This commit introduces test/common/internet.address, which includes a set of addresses for doing internet tests. These addresses can be overriden using NODE_TEST_* environment variables. PR-URL: nodejs#16390 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#16390 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit introduces test/common/internet.address, which includes a set of addresses for doing internet tests. These addresses can be overriden using NODE_TEST_* environment variables. PR-URL: #16390 Backport-PR-URL: #19706 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
This PR makes the addresses used by the internet tests configurable (via NODE_TEST_* environment variables), so it's easier to verify them within a firewall.
Also this moves most google.com references to nodejs.org.
Checklist
Affected core subsystem(s)
test