-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
test: do not use valid public hosts for timeout testing #2057
Conversation
I think they are tests that can rely on one. If it doesn't rely on one anymore, I figure it could be moved to parallel. |
gotConnect1 = true; | ||
socket1.destroy(); | ||
gotConnect = true; | ||
socket.destroy(); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could replace the callback with just assert.fail
.
LGTM |
PR-URL: #2057 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
landed in c786d63 |
Shouldn't this test be moved to |
@Fishrock123 see #2257 😄 |
A couple of assumptions I've made:
test/internet
directory: Is it just tests that rely on an internet connection but really shouldn't ideally? Or is that an incorrect assumption? (Is it documented anywhere?) Now that this one doesn't rely on a working internet connection, should it be moved totest/parallel
instead?Additional information that may be useful:
240.0.0.0
might, theoretically, be used at some future time. But that is unlikely. And even so, it's still a better choice for the foreseeable future than a valid Time-Warner IP, which is what it seems the previous one was.