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.

Sign up for GitHub

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

Jump to bottom

[flake] TestRouterHealthzEndpoint: address already in use #16290

Closed
tnozicka opened this issue Sep 12, 2017 · 3 comments
Closed

[flake] TestRouterHealthzEndpoint: address already in use #16290

tnozicka opened this issue Sep 12, 2017 · 3 comments
Assignees
@knobunc
Labels
component/routing kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1

Comments

@tnozicka
Copy link
Contributor 

=== RUN   TestRouterHealthzEndpoint
--- FAIL: TestRouterHealthzEndpoint (0.00s)
	router_test.go:937: Unable to start http server: listen tcp 172.18.11.173:8080: bind: address already in use

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/16129/test_pull_request_origin_end_to_end/2271/
@tnozicka tnozicka added component/routing kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels Sep 12, 2017
@tnozicka tnozicka mentioned this issue Sep 12, 2017
Closed
@jsafrane jsafrane mentioned this issue Sep 13, 2017
Merged
@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 20, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 22, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@knobunc knobunc

Labels
component/routing kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@openshift-bot @knobunc @tnozicka @openshift-ci-robot