Skip to content
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

unit: TestWaitsForAllInformersToBeSynced2 failure #16802

Closed
aveshagarwal opened this issue Oct 11, 2017 · 3 comments
Closed

unit: TestWaitsForAllInformersToBeSynced2 failure #16802

aveshagarwal opened this issue Oct 11, 2017 · 3 comments
Assignees
Labels
component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P1

Comments

@aveshagarwal
Copy link
Contributor

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/16778/origin-ci-ut-origin/121/

=== RUN   TestWaitsForAllInformersToBeSynced2
E1010 16:39:20.520697   27076 util.go:45] Metric for endpoint_controller already registered
E1010 16:39:20.672311   27076 controller_utils.go:1028] Unable to sync caches for endpoint controller
E1010 16:39:20.674951   27076 util.go:45] Metric for endpoint_controller already registered
E1010 16:39:20.826142   27076 controller_utils.go:1028] Unable to sync caches for endpoint controller
E1010 16:39:20.829545   27076 util.go:45] Metric for endpoint_controller already registered
E1010 16:39:21.015989   27076 controller_utils.go:1028] Unable to sync caches for endpoint controller
E1010 16:39:21.019504   27076 util.go:45] Metric for endpoint_controller already registered
--- FAIL: TestWaitsForAllInformersToBeSynced2 (0.67s)
	<autogenerated>:12: Expected 1 call, but got 0. Only the last call is recorded and checked.		
@aveshagarwal aveshagarwal added kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels Oct 11, 2017
@aveshagarwal
Copy link
Contributor Author

@sjenning

@aveshagarwal aveshagarwal changed the title TestWaitsForAllInformersToBeSynced2 failure unit: TestWaitsForAllInformersToBeSynced2 failure Oct 11, 2017
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2018
@sjenning
Copy link
Contributor

this isn't happening anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P1
Projects
None yet
Development

No branches or pull requests

6 participants