-
Notifications
You must be signed in to change notification settings - Fork 166
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
network differences resulting in test failures #2165
Comments
The difference in /etc/hosts is that -2 has its ipv6, ipv4 and intranet ip addresses listed as resolving to its own hostname whereas -1 doesn't. I've manually added in the entries for -1. 🤞 |
I'm going to optimistically close this. I usually watch node-daily-master closely enough that if this didn't fix it, I'll notice and re-open. Thanks, @rvagg! |
Happened again? This is on test-rackspace-ubuntu1604-x64-2
|
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Going to close this since it looks like its not recreated again for a long time. |
Network settings for test-rackspace-ubuntu1604-x64-1 and test-rackspace-ubuntu1604-x64-2 appear to be different, or at least I'm inferring that from the fact that the nightly internet test runs fail on test-rackspace-ubuntu1604-x64-2 but succeed on test-rackspace-ubuntu1604-x64-1.
Here's what a failure looks like:
https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/12019/console
The text was updated successfully, but these errors were encountered: