-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Tests flake registry #12372
Comments
https://travis-ci.com/github/etcd-io/etcd/jobs/396572378
|
https://travis-ci.com/github/etcd-io/etcd/jobs/396886611
|
https://travis-ci.com/github/etcd-io/etcd/jobs/396903952
|
https://travis-ci.com/github/etcd-io/etcd/jobs/397424709
|
https://travis-ci.com/github/etcd-io/etcd/jobs/397449189
|
https://travis-ci.com/github/etcd-io/etcd/jobs/397449193
|
https://travis-ci.com/github/etcd-io/etcd/jobs/403443329
|
https://travis-ci.com/github/etcd-io/etcd/jobs/403443330
|
https://travis-ci.com/github/etcd-io/etcd/jobs/403584630
|
…goroutines. Should solve the problem of flakes documented here: etcd-io#12372 (comment) ``` % (cd tests && env go test -short -timeout=3m -cpu=4 --race=true ./... -p=2) Unexpected goroutines running after all test(s). 1 instances of: go.etcd.io/etcd/v3/clientv3.(*watchGrpcStream).sendCloseSubstream(...) /go/src/go.etcd.io/etcd/clientv3/watch.go:464 +0x204 created by go.etcd.io/etcd/v3/clientv3.(*watchGrpcStream).closeSubstream /go/src/go.etcd.io/etcd/clientv3/watch.go:480 +0x21f FAIL go.etcd.io/etcd/tests/v3/integration/clientv3/examples 2.111s ``` The goroutine finishes automatically with timeout of 250ms.The change makes the test wait for it - if it still exists. Examples: https://travis-ci.com/github/etcd-io/etcd/jobs/397449189 https://travis-ci.com/github/etcd-io/etcd/jobs/397532784 https://travis-ci.com/github/etcd-io/etcd/jobs/397696506 https://travis-ci.com/github/etcd-io/etcd/jobs/403603526
https://semaphoreci.com/etcd-io/etcd/branches/pull-request-12451/builds/1
|
https://travis-ci.com/github/etcd-io/etcd/jobs/469558178
|
``` Unexpected goroutines running after all test(s). 1 instances of: syscall.Syscall(...) /usr/local/go/src/syscall/asm_linux_386.s:19 +0x5 syscall.Close(...) /usr/local/go/src/syscall/zsyscall_linux_386.go:285 +0x3d internal/poll.(*FD).destroy(...) /usr/local/go/src/internal/poll/fd_unix.go:77 +0x30 internal/poll.(*FD).decref(...) /usr/local/go/src/internal/poll/fd_mutex.go:213 +0x38 internal/poll.(*FD).Close(...) /usr/local/go/src/internal/poll/fd_unix.go:99 +0x43 net.(*netFD).Close(...) /usr/local/go/src/net/fd_posix.go:37 +0x49 FAIL go.etcd.io/etcd/tests/v3/integration/client 0.039s ``` ``` --- FAIL: TestServer_TCP_Secure_DelayTx (0.20s) server_test.go:110: took 128.026085ms with no latency server_test.go:125: took 62.980988ms with latency 50ms��5ms server_test.go:133: expected took1 128.026085ms < took2 62.980988ms (with latency) ``` etcd-io#12372
``` Unexpected goroutines running after all test(s). 1 instances of: syscall.Syscall(...) /usr/local/go/src/syscall/asm_linux_386.s:19 +0x5 syscall.Close(...) /usr/local/go/src/syscall/zsyscall_linux_386.go:285 +0x3d internal/poll.(*FD).destroy(...) /usr/local/go/src/internal/poll/fd_unix.go:77 +0x30 internal/poll.(*FD).decref(...) /usr/local/go/src/internal/poll/fd_mutex.go:213 +0x38 internal/poll.(*FD).Close(...) /usr/local/go/src/internal/poll/fd_unix.go:99 +0x43 net.(*netFD).Close(...) /usr/local/go/src/net/fd_posix.go:37 +0x49 FAIL go.etcd.io/etcd/tests/v3/integration/client 0.039s ``` ``` --- FAIL: TestServer_TCP_Secure_DelayTx (0.20s) server_test.go:110: took 128.026085ms with no latency server_test.go:125: took 62.980988ms with latency 50ms��5ms server_test.go:133: expected took1 128.026085ms < took2 62.980988ms (with latency) ``` etcd-io#12372
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
The purpose of this issue is to track different forms of flakes we observe in the tests.
This should allow to identify frequent patterns to fix:
Format:
https://link-to-CI
The text was updated successfully, but these errors were encountered: