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

leak readloop goroutine when integration testing #1853

Closed
yichengq opened this issue Dec 4, 2014 · 4 comments
Closed

leak readloop goroutine when integration testing #1853

yichengq opened this issue Dec 4, 2014 · 4 comments
Assignees
@yichengq
Labels
area/testing
Milestone
v2.2.0-alpha0

Comments

@yichengq
Copy link
Contributor

yichengq commented Dec 4, 2014

https://travis-ci.org/coreos/etcd/builds/42929844

It really needs some time to debug and fix it. We will skip the check as the first step.
@yichengq yichengq mentioned this issue Dec 4, 2014
Merged
@xiang90 xiang90 added this to the v3.0.0-maybe milestone Dec 23, 2014
@xiang90 xiang90 modified the milestones: v2.1.0, v3.0.0-maybe Jan 15, 2015
@xiang90
Copy link
Contributor

xiang90 commented Mar 13, 2015

@yichengq Have we reported this to golang upstream yet?

@yichengq
Copy link
Contributor Author

I reported it here: https://groups.google.com/forum/#!topic/golang-nuts/YKASjGmjPXw
I am trying to replay it with simple go program now. Will open an issue in golang repo when i make it.

@yichengq yichengq self-assigned this Mar 25, 2015
@yichengq
Copy link
Contributor Author

It is reported here:
golang/go#10457
I will keep track of the issue.

@yichengq yichengq modified the milestones: v2.2.0, v2.1.0-alpha0 Apr 14, 2015
@xiang90
Copy link
Contributor

xiang90 commented Apr 14, 2015

closing this since it is being tracked in golang repo.

@xiang90 xiang90 closed this as completed Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yichengq yichengq

Labels
area/testing
Milestone
v2.2.0-alpha0
Development

No branches or pull requests
2 participants
@yichengq @xiang90