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

TestWatchFromZeroAndNoneZero {etcd3} #31079

Closed
k8s-github-robot opened this issue Aug 21, 2016 · 4 comments
Closed

TestWatchFromZeroAndNoneZero {etcd3} #31079

k8s-github-robot opened this issue Aug 21, 2016 · 4 comments
Assignees
@hongchaodeng
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

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/16041/

Failed: TestWatchFromZeroAndNoneZero {etcd3}

watcher_test.go:297: #0: time out after waiting 30s on ResultChan
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Aug 21, 2016
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/16045/

Failed: TestWatchFromZeroAndNoneZero {etcd3}

watcher_test.go:297: #0: time out after waiting 30s on ResultChan

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/16065/

Failed: TestWatchFromZeroAndNoneZero {etcd3}

watcher_test.go:297: #0: time out after waiting 30s on ResultChan

@k8s-github-robot k8s-github-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Aug 22, 2016
@feiskyer feiskyer mentioned this issue Aug 22, 2016
Merged
@mikedanese mikedanese assigned hongchaodeng and unassigned apelisse Aug 22, 2016
@brendandburns brendandburns mentioned this issue Aug 23, 2016
Merged
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-test-go/16155/

Failed: TestWatchFromZeroAndNoneZero {etcd3}

watcher_test.go:297: #0: time out after waiting 30s on ResultChan

@k8s-github-robot k8s-github-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 24, 2016
@hongchaodeng hongchaodeng mentioned this issue Aug 24, 2016
Merged
k8s-github-robot pushed a commit that referenced this issue Aug 24, 2016
Merge pull request #31323 from hongchaodeng/testwatch
9a9c989 
Automatic merge from submit-queue

Separate test watch from zero and nonzero

Recently there was spike flakes for this. See #31079.

This is to split the test into two units for further digging. We need to know which one is problematic, or both.
@krousey krousey mentioned this issue Aug 25, 2016
Merged
@lavalamp
Copy link
Member

This test doesn't exist after #31323

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

@hongchaodeng hongchaodeng

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
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lavalamp @hongchaodeng @apelisse @pwittrock @k8s-github-robot