-
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
java.net.ConnectException: Connection timed out on jenkins-workspace machines #3037
Comments
The expected output, without the ConnectException, is
It's unclear to me whether the exception is occurring during the git step or the subsequent fetch of the VersionSelectorScript.groovy script. |
I put an extra print statement in the Groovy Script Matrix Executor Strategy script for https://ci.nodejs.org/job/node-test-commit-linux/ so that it starts:
(the "Fetching..." line is the addition). https://ci.nodejs.org/job/node-test-commit-linux/47624/console failed:
so it looks like it's the part of the Groovy script that fetches |
Possibly related:
|
This one as well: |
Maybe this should be reported to GitHub? |
How does one do that? |
I'd try with https://support.github.com/contact/bug-report |
Assuming it's https://raw.githubusercontent.com/ that sometimes never responds. |
I've opened a ticket (https://support.github.com/ticket/personal/0/1810165) but it doesn't look like it is visible to anyone else despite selecting "Node.js" as the "Account or organization" 😞 |
I have a sporadic command line recreate on one of our Digital Ocean droplets with curl -v. (Used -4 on this host as it doesn't have a working IPv6 route):
Eventually this succeeds but only after the first few attempts to 185.199.110.133 and 185.199.111.133 timed out. 185.199.109.133 succeeded (note that the third octet is different in each case). |
It appears that the recent builds today/last night are not encountering this issue, hopefully it's resolved itself 🤞. (FTR we haven't done anything to fix this and GH haven't responded to the ticket I raised.) |
Currently we're seeing a spate of
java.net.ConnectException: Connection timed out
on the jenkins-workspace machines in the CI. At first I thought it was the new jenkins-workspace machines but taking those offline and putting the old ones back online shows those are also exhibiting the issue.e.g. https://ci.nodejs.org/job/node-test-commit-arm-debug/4135/console
test-packetnet-ubuntu1804-x64-1
https://ci.nodejs.org/job/node-test-commit-linux/47617/console
test-ibm-ubuntu1804-x64-1
It's not consistent (several jobs running on the same jenkins-workspace machines pass) but often that I've not had a clean node-test-commit run in the last couple of hours.
Note that this git server being contacted prior to the time outs is github.com and not the temp binary repository (which is only used by the windows-fanned and arm-fanned jobs).
The text was updated successfully, but these errors were encountered: