-
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
github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/controller/node.TestCancelAndReadd #13966
Comments
github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/controller/node.TestCancel (from github.com_openshift_origin_vendor_k8s.io_kubernetes_pkg_controller_node)
Seen there: https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1444/ |
|
I thought this was fixed upstream??? |
They are literally ignoring it upstream: kubernetes/kubernetes#51704 /shrug This flake is becoming really annoying. @derekwaynecarr can we push forward either fixing it (here or upstream I don't care) or disable? |
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_pull_request_origin_check/1568
The text was updated successfully, but these errors were encountered: