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

unittest flake: resttest.go: unexpected timeout from result channel #32772

Closed
jsafrane opened this issue Sep 15, 2016 · 3 comments
Closed

unittest flake: resttest.go: unexpected timeout from result channel #32772

jsafrane opened this issue Sep 15, 2016 · 3 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@jsafrane
Copy link
Member

From https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/31978/kubernetes-pull-test-unit-integration/44935/

2016-09-15 01:47:51.549894 I | etcdserver: published {Name:node4735261938323256311 ClientURLs:[unix://127.0.0.1:21012.7913.sock]} to cluster c9c2d39b7c65124f
2016-09-15 01:47:51.598332 W | etcdserver: apply entries took too long [11.933395ms for 1 entries]
2016-09-15 01:47:51.599521 W | etcdserver: avoid queries with large range/delete range!
2016-09-15 01:48:23.871044 I | integration: terminating node4735261938323256311 (unix://localhost:node4735261938323256311.sock.bridge)
2016-09-15 01:48:23.878286 I | integration: terminated node4735261938323256311 (unix://localhost:node4735261938323256311.sock.bridge)
--- FAIL: TestWatch (32.41s)
    resttest.go:1251: unexpected timeout from result channel

The test usually takes 2-3 seconds, here it took 32 s. It happened when testing pr #31978, IMO it's unrelated to the bug.

@jsafrane jsafrane added the kind/flake Categorizes issue or PR as related to a flaky test. label Sep 15, 2016
@pwittrock pwittrock added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Sep 19, 2016
@pwittrock
Copy link
Member

I am encountering this a lot and it is getting painful.

@calebamiles
Copy link
Contributor

@saad-ali, this issue should probably be closed. The associated PR has already been merged and the PR test grid was green except for GKE tests which were non blocking

@saad-ali
Copy link
Member

saad-ali commented Nov 3, 2016

ACK. Closing

@saad-ali saad-ali closed this as completed Nov 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

4 participants