-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
TestRouter integration flake #8502
Comments
This may be the go reuse of closed network transactions, i.e. a test side error vs a server side (if you are using pooled connections you can occasionally fail to get a real connection). |
@marun can you take a look at this please? |
Given that this hasn't been seen since May I don't see the value in investigating this further. If it reappears, we can reopen. |
Hit it in https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_integration/8777/consoleFull:
Reopening. |
But I'm lowering the prio to p2, since it's not permanent or anything. |
A different failure mode for this test:
|
Seems like it's flaking a lot today, increasing priority. |
Seems like the latest failure is tracked in #12236 - resetting priority for this. |
hit this again in https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_integration/1927/consoleFull#165939508756bf4006e4b05b79524e5923
|
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 |
from https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/5581/consoleFull#112541649156bf4006e4b05b79524e5923
The text was updated successfully, but these errors were encountered: