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

Add event checking to density tests #6637

Closed
rrati opened this issue Apr 9, 2015 · 1 comment
Closed

Add event checking to density tests #6637

rrati opened this issue Apr 9, 2015 · 1 comment
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@rrati
Copy link

rrati commented Apr 9, 2015

Currently the density tests are ok if all the pods come up eventually. We should verify there are no failure/error events while the pods are coming up. This could indicate issues dealing with the number of pods and should be investigated.
rrati pushed a commit to rrati/kubernetes that referenced this issue Apr 9, 2015
Add checking of events after all pods started to verify no failures in
dfdd36e 
density test kubernetes#6637
@rrati rrati mentioned this issue Apr 9, 2015
Merged
@lavalamp lavalamp added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. misc/perf-1.0 labels Apr 9, 2015
@davidopp davidopp added team/master priority/backlog Higher priority than priority/awaiting-more-evidence. labels Apr 12, 2015
rrati pushed a commit to rrati/kubernetes that referenced this issue Apr 21, 2015
Add checking of events after all pods started to verify no failures in
93d1040 
density test kubernetes#6637
rrati pushed a commit to rrati/kubernetes that referenced this issue Apr 21, 2015
Bounded the loop waiting for all events to be logged and print a warning
23c5b77 
if not all are logged 10 minutes after all pods are started kubernetes#6637
rrati pushed a commit to rrati/kubernetes that referenced this issue Apr 21, 2015
Converted from continually listing events to using an Informer kubern…
020ba6a 
…etes#6637
@lavalamp
Copy link
Member

#6638 has been merged, and there's already an issue filed for followup actions, so I think we can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rrati @lavalamp @davidopp