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

TestStreamWriterAttachBadOutgoingConn: working = true, want false #6187

Closed
heyitsanthony opened this issue Aug 15, 2016 · 1 comment
Closed
Assignees
Milestone

Comments

@heyitsanthony
Copy link
Contributor

via semaphore (https://semaphoreci.com/coreos/etcd/branches/master/builds/781)

--- FAIL: TestStreamWriterAttachBadOutgoingConn (0.02s)
    stream_test.go:109: working = true, want false
    stream_test.go:112: failed to close the underlying connection

Possibly triggered by #6175

@xiang90 xiang90 added this to the v3.1.0 milestone Aug 15, 2016
@gyuho
Copy link
Contributor

gyuho commented Aug 17, 2016

2016-08-15 23:13:02.827773 E | rafthttp: failed to write 1 on stream Message (blah)
2016-08-15 23:13:02.828097 I | rafthttp: peer 1 became inactive
2016-08-15 23:13:02.841645 W | rafthttp: lost the TCP streaming connection with peer 1 (stream Message writer)
2016-08-15 23:13:02.841790 I | rafthttp: stopped streaming with peer 1 (writer)

Isn't it already deactivating the status after we send message to msgc?

(cr *streamReader) decodeLoop never got called based on the logs.

Maybe cw.close() took more than 10ms before it sets working as false?

@heyitsanthony heyitsanthony self-assigned this Aug 18, 2016
heyitsanthony pushed a commit to heyitsanthony/etcd that referenced this issue Aug 18, 2016
heyitsanthony pushed a commit to heyitsanthony/etcd that referenced this issue Aug 18, 2016
heyitsanthony pushed a commit to heyitsanthony/etcd that referenced this issue Aug 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants