-
Notifications
You must be signed in to change notification settings - Fork 4.7k
flake: unable to connect to service idling-echo: getsockopt: connection refused #12137
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
Comments
Dropping the priority because this shouldn't block the release. I'm actively investigating it at the moment though. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/869/consoleFull
Could be related to #12112, idling and unidling seems to be flaky these days.
The text was updated successfully, but these errors were encountered: