-
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
Jenkins java.io.IOException: remote file operation failed #173
Comments
Could potentially be addressed by restarting Jenkins, like #169 |
@nodejs/jenkins-admins |
happening a lot recently, perhaps we need to update slave.jar |
Haven't seen these in a good while. Fwiw, we've updated slave.jar's throughout our fleet but is likely unrleated. |
This just occured again (spotted by @Trott): https://ci.nodejs.org/job/node-test-binary-arm/159/RUN_SUBSET=1,nodes=pi2-raspbian-wheezy/console |
Is it useful to keep reporting these here as they occur or is that just noise? |
interesting they are just pi2-9 and pi2-2 so far @Trott feel free to keep on reporting if they keep showing up, a pattern may be interesting |
@Trott - seen anything of this recently? |
Haven't noticed it lately, but I haven't been looking for it either. |
Speaking of the devil: https://ci.nodejs.org/job/node-test-binary-arm/RUN_SUBSET=addons,nodes=pi2-raspbian-wheezy/902/console Edit: again just on ARM it seems. Are these perhaps trying to all pull at the same time? |
Sorry to bump into this thread, this is a last resort... was this ever resolved? If so how? I'm seeing the same exception stack trace in my Jenkins jobs, though running in OS X, so not ARM:
|
Haven't seen these in a long while, but others; "remote host closed connection" |
Again:
|
bump Did you guys ever figure out what was going on here? Any Jenkins JIRA tickets? |
@chr0n1x afraid not, there's also not much we can do about this, you'd need to raise (or find) an issue in Jenkins. |
@gibfahn one thing that I tried was this. I seems to have helped with what I was seeing on my instance. In my case it was many many many slaves spinning up and the connections to them not terminating fast enough, getting stuck in the |
Has this happened recently? Otherwise I think this can be closed |
Closing due to inactivity. Please reopen if this is still needed :) |
I've found a possible workaround — restarting the java worker ( |
A bit more info (for posterity). Looking at these seemingly key lines from the most recent trace:
|
I had to take one of the smartos16 machines offline yesterday because of this, every build failed the same. No matter what I did on the node fixed the problem, including updating slave.jar. I got nuttin'. |
This is an intermittent failure that I have seen in Jenkins for a long time. One instance here: https://ci.nodejs.org/job/node-test-commit-arm/nodes=pi1-raspbian-wheezy-1_of_2/407/console
The text was updated successfully, but these errors were encountered: